move-to-worktree

Git worktrees let you isolate feature branches into a .worktrees directory, detaching HEAD to move the checked-out branch out of the project root and restoring master. This prevents accidental development in the repository root.

Yes, you can supply a nested subdirectory path like logging/refactor-logging when creating git worktrees, and parent directories are created automatically so the feature branch runs in an organized separate worktree.

The process refuses to run when there are uncommitted changes, ensuring safety before detaching HEAD and creating the worktree. You must commit or stash changes first to proceed with branch isolation.

Yes, creating a worktree under .worktrees adds that directory to .gitignore if needed, keeping repository hygiene intact so the isolated feature branch directories are excluded from git tracking.

You should not use this approach when already on master or main, when HEAD is detached, or when the target worktree path already exists. The process refuses to run in these states to prevent overwriting or conflicts.

Moving feature work into isolated git worktrees under .worktrees keeps the project root checked out on master, preventing accidental development and simplifying branch isolation for safer repository management.