Re: [PATCH v5 1/4] fetch: Protect branches checked out in all worktrees

From: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date: Nov 10, 2021, 03:56 UTC
Message-ID: <211110.8635o4k6i7.gmgdl@evledraar.gmail.com>
In-Reply-To: <20211109230941.2518143-1-andersk@mit.edu>

On Tue, Nov 09 2021, Anders Kaseorg wrote:

Show 10 quoted lines

> Refuse to fetch into the currently checked out branch of any working
> tree, not just the current one.
>
> Fixes this previously reported bug:
>
> https://public-inbox.org/git/cb957174-5e9a-5603-ea9e-ac9b58a2eaad@mathema.de
>
> As a side effect of using find_shared_symref, we’ll also refuse the
> fetch when we’re on a detached HEAD because we’re rebasing or bisecting
> on the branch in question. This seems like a sensible change.

Missing tests though, would be nice to have a test that saw what happened when the branch is in that "git bisect start" or rebasing state.

Also what those commands to if the branch is updated, e.g. with git-update-ref.