using-git-worktrees

To create an isolated git worktree, the system detects your project context, selects an appropriate directory, verifies gitignore safety, checks out the target branch, and runs setup commands automatically. This keeps feature work separate from your main workspace.

A git worktree is an isolated workspace linked to your repository that lets you work on multiple branches simultaneously. You need a git worktree when starting feature work or safely testing changes without affecting your main branch's working directory.

To prevent accidental commits of worktree contents, the setup verifies that the selected worktree directory is properly ignored by your project's gitignore configuration before creating the worktree and checking out the branch.

Yes, you can use a global directory instead of a project-local worktree. The setup supports both project-local paths like .worktrees or worktrees, and global locations, automatically detecting context and selecting an appropriate directory.

Yes, the worktree setup runs project bootstrapping commands automatically. When relevant, it detects and executes setup commands like npm, cargo, or go to bootstrap the new worktree environment after checking out the branch.

The best way to manage multiple git branches for parallel development is using isolated git worktrees. This approach creates separate working directories for each branch, allowing you to experiment and test changes safely without switching branches in your main workspace.