git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / Atom feed
* Worktrees attached to bare repo don't work
@ 2020-09-12 19:59 Lobachevksiy Vitaliy
  2020-09-13  4:49 ` Eric Sunshine
  0 siblings, 1 reply; 2+ messages in thread
From: Lobachevksiy Vitaliy @ 2020-09-12 19:59 UTC (permalink / raw)
  To: git

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`

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Worktrees attached to bare repo don't work
  2020-09-12 19:59 Worktrees attached to bare repo don't work Lobachevksiy Vitaliy
@ 2020-09-13  4:49 ` Eric Sunshine
  0 siblings, 0 replies; 2+ messages in thread
From: Eric Sunshine @ 2020-09-13  4:49 UTC (permalink / raw)
  To: Lobachevksiy Vitaliy; +Cc: Git List

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/

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-09-13  4:50 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-09-12 19:59 Worktrees attached to bare repo don't work Lobachevksiy Vitaliy
2020-09-13  4:49 ` Eric Sunshine

git@vger.kernel.org list mirror (unofficial, one of many)

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://public-inbox.org/git
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 git git/ https://public-inbox.org/git \
		git@vger.kernel.org
	public-inbox-index git

Example config snippet for mirrors.
Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.version-control.git
	nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git
	nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git
	nntp://news.gmane.io/gmane.comp.version-control.git
 note: .onion URLs require Tor: https://www.torproject.org/

code repositories for the project(s) associated with this inbox:

	https://80x24.org/mirrors/git.git

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git