se-worktree

To create an isolated git worktree, run the bundled script which fetches your feature branch from origin and sets up a per-branch worktree under the .worktrees directory. This enables parallel development without altering your main checkout.

Using git worktrees is the best way to review pull requests safely. The script creates an isolated worktree under .worktrees, fetches the PR branch from origin, and configures the environment so your main checkout remains completely untouched.

When setting up a new git worktree, the script automatically copies environment files such as .env and .env.local from the main repository into the new worktree directory. It skips .env.example files to ensure your local secrets are available.

Yes, the worktree automation handles dev-tools trust by applying branch-aware safety rules. It automatically trusts configurations from trusted bases or prompts you for manual review when setting up isolated worktrees for tools like mise and direnv.

Yes, you can prevent .worktrees from cluttering your git status. The script automatically adds the .worktrees directory to your root .gitignore file, ensuring the new worktree folders do not appear as untracked files in your main repository.

Isolated worktrees allow you to maintain separate working directories for each branch simultaneously, preventing context loss from stashing. They include branch-specific .env files and dev-tool trust configurations, allowing you to test changes in parallel without checkout conflicts.