A feature band preserves staged, unstaged and untracked work while a separate hotfix starts at release commit B, reproduces failure, then passes after repair.

Use a worktree for a hotfix without disturbing a feature

A hotfix need not displace unfinished feature work from its directory. A linked worktree can start from a chosen release commit while the original directory retains its staged changes, unstaged edits, and untracked files. The workflow succeeds when the fix is tested on the correct baseline and the original work remains intact. Merely creating a second folder does not establish either result. ...

November 6, 2027 · 6 min · XB Field Notes
One shared repository connects to main and review. Both retain their own HEAD, index and working files.

Git worktrees share a repository, not a checkout

A linked worktree gives one Git repository another working directory, with its own checked-out state. That lets a feature, release, or review stay open alongside other work without repeatedly replacing the same files. The useful boundary is separate working files and staging, not complete isolation. Objects, many references, and ordinary repository configuration are shared, so operations need to respect both the local workspace and the common repository. ...

July 26, 2027 · 5 min · XB Field Notes