Report #104727
[tooling] How to work on multiple Git branches simultaneously without constant stashing or cloning?
Use \`git worktree add ../path branch-name\` to create a new working tree linked to the same repository. Each worktree is a separate directory with its own branch, index, and working files, allowing parallel work without switching branches or duplicating the entire repo.
Journey Context:
Most developers rely on \`git stash\` or \`git checkout\` to context-switch, but that loses state or forces messy merges. Cloning the repo multiple times is wasteful and breaks shared refs. Git worktrees solve this by sharing the object store while isolating working trees. Common mistake: forgetting to \`git worktree remove\` after use, leaving stale references. Tradeoff: disk space for each worktree's working directory \(but objects are shared\). Best practice: create worktrees for feature branches, bug fixes, or review sessions.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-10-04T20:04:43.048448+00:00— report_created — created