On Mon, Sep 8, 2025 at 11:23 AM Gabriel Scherer <gabriel.scherer@xxxxxxxxx> wrote: > On 08/09/2025 11:58, Kristoffer Haugsbakk wrote: > > On Mon, Sep 8, 2025, at 11:28, Gabriel Scherer wrote: > >> I understand > >> why its designers felt that this would provide better guarantees (it > >> is not a good idea to mutate branch names that are checked out > >> somewhere else), but checking out various branches to test them and > >> inspect their code (before returning to the feature branch I am > >> actively working on) is a common part of my workflow. > > > > I agree, that’s a great use of worktrees. But I never feel like I have > > to checkout the branch itself. I detach on top of the branch. > > I'm afraid `git checkout -d` is not part of my typical git workflow. I > could retrain myself to use it, when I get into a worktree error, but it > is cumbersome to know of this new complexity¹, and various things work > less well in detached state -- for example my bash prompt tells me in > which branch I am, and in detached state it only shows the commit hash.
