From bf08abac565fa64eeaa56d2eb21ce1a9d2371358 Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Wed, 18 Jan 2023 23:23:46 -0800 Subject: [PATCH] branch: document `-f` and linked worktree behaviour "git branch -f name start" forces to recreate the named branch, but the forcing does not defeat the "do not touch a branch that is checked out elsewhere" safety valve. Signed-off-by: Junio C Hamano --- Documentation/git-branch.txt | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt index 12c5f84e3b..2aaf13b45d 100644 --- a/Documentation/git-branch.txt +++ b/Documentation/git-branch.txt @@ -123,6 +123,10 @@ OPTIONS points to a valid commit. In combination with `-m` (or `--move`), allow renaming the branch even if the new branch name already exists, the same applies for `-c` (or `--copy`). ++ +Note that 'git branch -f []', even with '-f', +refuses to change an existing branch `` that is checked out +in another worktree linked to the same repository. -m:: --move::