# Worktrees attached to bare repo don't work 2 messages from 2020-09-12 to 2020-09-13. Participants: Lobachevksiy Vitaliy, Eric Sunshine. Thread: https://gitlist.dev/t/54233 ## Lobachevksiy Vitaliy, 2020-09-12 19:59 Subject: Worktrees attached to bare repo don't work Message-ID: <3b57a5b2-a34e-de95-38c7-9bc6923a8eba@yandex.ru> URL: https://gitlist.dev/e/3b57a5b2-a34e-de95-38c7-9bc6923a8eba%40yandex.ru ``` 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` ``` ## Eric Sunshine, 2020-09-13 04:49 Subject: Re: Worktrees attached to bare repo don't work Message-ID: URL: https://gitlist.dev/e/CAPig%2BcRqkzPzNX8UN4OcgEOOKbtZRLCjNNiZsOVkGBy0pvsEkQ%40mail.gmail.com In-Reply-To: <3b57a5b2-a34e-de95-38c7-9bc6923a8eba@yandex.ru> ``` On Sat, Sep 12, 2020 at 4:01 PM Lobachevksiy Vitaliy 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/ ```