Re: [PATCH] bisect: fix "reset" when branch is checked out elsewhere

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 26, 2023, 17:13 UTC
Message-ID: <xmqqr0vhb4nx.fsf@gitster.g>
In-Reply-To: <xmqqzga5b4yz.fsf@gitster.g>

Junio C Hamano <gitster@pobox.com> writes:

> the branch itself.  And more importantly, the branch being checked
> out in another worktree and modified there should not break the
> bisection, EXCEPT that the final "git bisect reset" (without
> arguments) would fail if the other worktree removed the branch.

And "bisect reset [<branch>]" (with or without arguments) should not ignore other worktrees when it runs "checkout" internally. You might have done

    * checkout 'work' in worktree A
    * start bisection of it there
    * checkout 'work' in worktree B
    * finish bisection of 'work' in worktree A
    * "git bisect reset"

and the third step should allow you work on 'work' in the other worktree, but then the last step should not allow 'work' to be checked out in two places (it is OK for the user to use "git bisect reset main" and then "git checkout --ignore-other work" to work it around, of course, but the default should be safe).

Hmm?