Detached head worktrees do not appear in worktree popup

[connortsui20]

Reproduction steps

Recently, there was an update (I do not know which PR, please let me know and I can update this description) that moved git worktrees from the "recent projects" popup to a new(?) git worktrees popup. I would typically use the recent projects popup to open worktrees.

That change was fine, but I've noticed that if a git worktree is not on a branch (for example, a detached head), it doesn't appear on the worktree popup. So now that worktree doesn't appear on ANY popup (that I am aware of).

Current vs. Expected behavior

See reproduction steps.

I would expect the detached head worktree to still appear on the worktrees popup. Because now (AFAIK) the only way for me to open it is via my filesystem.

Zed version and system specs

Zed: v0.230.1+stable.210.bf3a14350a4fa4b67747afe2e50128fb8fea4fa3 (Zed)
OS: macOS 15.7.3
Memory: 128 GiB
Architecture: aarch64

[esamattis]

I can confirm. There is no longer a way to open git worktrees from Zed.

My directory structure is following

~/code/project # actual git clone
~/code/project-gw1 # worktree checkout of ~/code/project
~/code/project-gw2 # worktree checkout of ~/code/project

The only way to open the worktrees now is from the CLI zed -n ~/code/project-gw1

Here are steps to reproduce:

mkdir repro
cd repro
git clone https://github.com/zed-industries/awesome-gpui.git

# create some worktrees
cd awesome-gpui
git worktree add -B gw1 ../awesome-gpui-gw1
git worktree add -B gw1 ../awesome-gpui-gw1
cd ..

# open each once in zed
zed awesome-gpui
zed awesome-gpui-gw1
zed awesome-gpui-gw2

And the worktrees are nowhere to be seen

They used to appear at least in "Recents Projects" which I used.

[yeskunall]

Yeah, I think I can reproduce what you’re saying --

mkdir -p /tmp/worktree-repro && cd /tmp/worktree-repro && rm -rf awesome-gpui awesome-gpui-gw1 awesome-gpui-gw2 awesome-gpui-detached && git clone --quiet https://github.com/zed-industries/awesome-gpui.git 

cd /tmp/worktree-repro/awesome-gpui && git worktree add -B gw1 ../awesome-gpui-gw1 && git worktree add -B gw2 ../awesome-gpui-gw2 && git worktree add --detach ../awesome-gpui-detached HEAD && echo "---" && git worktree list --porcelain


Preparing worktree (new branch 'gw1')
HEAD is now at 95839b3 Sort developer tools
Preparing worktree (new branch 'gw2')
HEAD is now at 95839b3 Sort developer tools
Preparing worktree (detached HEAD 95839b3)
HEAD is now at 95839b3 Sort developer tools
---
worktree /private/tmp/worktree-repro/awesome-gpui
HEAD 95839b30d2ba709379eccfcafe4d0e4c61d4cfb6
branch refs/heads/main

worktree /private/tmp/worktree-repro/awesome-gpui-detached
HEAD 95839b30d2ba709379eccfcafe4d0e4c61d4cfb6
detached

worktree /private/tmp/worktree-repro/awesome-gpui-gw1
HEAD 95839b30d2ba709379eccfcafe4d0e4c61d4cfb6
branch refs/heads/gw1

worktree /private/tmp/worktree-repro/awesome-gpui-gw2
HEAD 95839b30d2ba709379eccfcafe4d0e4c61d4cfb6
branch refs/heads/gw2

Notice in the porcelain output that awesome-gpui-detached has detached instead of branch refs/heads/....

--

Related:

• Fix usability issues with automatically-created git worktrees #51775
• multiworkspace: Don't destroy workspace when git worktree is detached head #51977

Filters detached worktrees out of the worktree picker UI, preserving the existing product decision to only show branch-based worktrees there

See #51977 for Eric’s (@/eholk) comment.

I’m led to believe what you guys are reporting is still a bug, tho, and not an intentional choice. Maybe I’m wrong?