using-git-worktrees

To create an isolated git workspace, you can set up a linked worktree that separates new feature changes from your current branch. This detects existing isolation, prefers native worktree tooling, and falls back to git worktree add with submodule checks and baseline testing.

A git worktree is an isolated workspace linked to your repository that allows simultaneous work on multiple branches. You need a worktree when running branching experiments or starting implementation plans that require separated changes without polluting your current checkout state.

Yes, you can use git worktrees with submodules. The workspace creation process includes specific submodule checks to ensure dependencies are handled correctly, verifying project-local worktree directories are ignored and running setup steps before baseline testing begins.

Yes, the git worktree setup performs ignore verification to ensure project-local worktree directories are properly ignored. It handles setup steps and checks the baseline before work starts, preventing untracked workspace files from polluting your repository status.

The best way to manage isolated feature branches is using git worktrees to create separate working directories for each branch. This approach detects if you are already inside a linked worktree, chooses native worktree tooling first, and falls back to standard git worktree creation.

You should set up an isolated workspace to prevent feature work from polluting your current repository state. This ensures separated changes in the existing repository, applying baseline testing and setup verification before implementation begins to maintain a clean working environment.