Worktrees attached to bare repo don't work

Worktrees attached to bare repo don't work

[Lobachevksiy Vitaliy]

I have a bare repository and several worktrees attached to it. That was
working fine until recent update. Now when I try virtually any git
command like `git status` in any attached worktree, or even in a new
one, it prints `fatal: this operation must be run in a work tree`.
The workaround is simply `git config --worktree --add core.bare false`
in each worktree.

I have git version 2.28.0 on Void Linux (musl, amd64).

-- 
Vitaliy `numzero`

Re: Worktrees attached to bare repo don't work

[Eric Sunshine]

On Sat, Sep 12, 2020 at 4:01 PM Lobachevksiy Vitaliy <numzer0@yandex.ru> wrote:
> I have a bare repository and several worktrees attached to it. That was
> working fine until recent update. Now when I try virtually any git
> command like `git status` in any attached worktree, or even in a new
> one, it prints `fatal: this operation must be run in a work tree`.
> The workaround is simply `git config --worktree --add core.bare false`
> in each worktree.

This is happening because you have apparently set the configuration
variable extensions.worktreeConfig to true. As far as I can tell by
reading the "Configuration File" section of the "git worktree"
documentation and by consulting the commit[1] which introduced
extensions.worktreeConfig, this is working as intended. According to
the "git worktree" documentation, configuration core.bare is no longer
specially filtered out when inside a worktree once
extensions.worktreeConfig is enabled, so you need to move the
core.bare=true setting out of the bare.git/config and into
bare.git/config.worktree to prevent the worktrees from seeing that
setting. Once that's done, you don't need the per-worktree
core.bare=false setting you've been using as a workaround.

[1]: https://lore.kernel.org/git/20181021140228.24941-3-pclouds@gmail.com/