git-worktrees

Git worktrees let you create isolated working directories for each branch, keeping changes separate without stashing. Use git worktree add -b feature/name ../path main to create a new worktree, then switch between directories to context-switch instantly while each branch maintains its own state.

Worktrees enable parallel development by housing each branch in its own directory. Run tests in one worktree while making changes in another simultaneously, eliminating the need to switch branches and rebuild each time you want to test different features.

Use worktrees when you need concurrent feature work, urgent fixes alongside ongoing development, or frequent context switching. Worktrees avoid stashing overhead and let you keep multiple branches checked out simultaneously, making them ideal for parallel testing and isolated development workflows.

Navigate worktrees with git worktree list to see all active branches and their paths. Remove completed worktrees using git worktree remove, and run git worktree prune to clean up stale entries and orphaned administrative files from deleted worktrees.

Yes, worktrees work with any repository that has Git with worktree support. You can add worktrees to an existing repo by running git worktree add from your main directory; each new worktree branches from an existing branch like main or develop.

Worktrees cannot share the same branch across multiple trees, and some operations like git fetch may affect all worktrees. Additionally, deleting a worktree's directory without using git worktree remove leaves orphaned administrative files that must be pruned manually.