[Feature Request] Hide worktree branch in main view

[besttof]

I like that Fork has such a neat, seamless way of working with worktrees, but it seamlessness has bitten and/or confused me on more than one occasion.

Because the branch that is checked out in a worktree is listed under the worktrees section (where it makes sense to me) and in your normal local branches list, I missed that I didn’t just switch to a branch but actually switched to another folder and tab in Fork. In one occasion it caused me to accidentally discard local changes in the wrong directory.

While those mistakes are completely my own fault, I’d appreciate it if a UI design helps me prevent those. I think that not displaying a worktree branch in the main list, but only in the worktrees section, could solve that. But any change to make the distinction between a normal branch and worktree branches would be greatly appreciated.

Maybe related to #2585

[DanPristupov]

I think that not displaying a worktree branch in the main list, but only in the worktrees section, could solve that.

I think that the branches section must show all branches. The user may want to navigate to that branch, diff to it, push it, etc.

[besttof]

Sure but they can also do that when it is displayed under the worktree section? I’m not arguing for not making the branch accessible from the main repo window; I’m just asking for a way to make it more clear you’re dealing with a worktree branch (because it has confused me and, admittedly by my own doing, lost me quite a bit of work)

[DanPristupov]

Sure but they can also do that [navigate, diff push?] when it is displayed under the worktree section?

No, you can't diff to a worktree, you can't push a worktree, etc

Not sure I understand, may be I'm missing something. Worktree is a worktree, branch is a branch. Worktree != branch. Worktree is just a different working directory, it's not related to branches.

[besttof]

I understand my issue is somewhat hard to explain... I'll try my best.

I am aware that a worktree is not the same as a branch. However, a worktree is always the checkout of a single branch and you can't check out that branch in another worktree or your main repository. Here the example branch is checked out in a worktree but there is no visual indication that if I'd double click it, it will change the current working directory (and related local changes)

Maybe because I work with Unity projects a lot, but those local changes are part of my process and often also things you get into the habit of casually discarding. In my case I was not present enough to realise I switched not only from branch but also from working directory and discarded my changes under the wrong assumptions.

I think there have been subtle changes to the worktree displays since then, not sure if, or what, changed since then. I am pretty sure I won't notice the newer changes too becaue my attention does not linger on the side-panel after I switch branches.

Maybe group the branches that are in worktrees under a different header? Or give them a different icon? Or make it an option to hide them in the main view / make the worktree listing also expose the branch functionality? I am honestly not sure what the best or most feasible solution is.

I hope that better explains my issue?