ce-worktree

To isolate feature branch work, you can provision a git worktree under a dedicated directory. This creates an isolated workspace linked to your branch, keeping your main checkout completely untouched while you experiment or review PRs.

When creating a new git worktree, the process automatically copies your .env files from the main repository into the new workspace. It backs up any existing environment files it encounters and skips .env.example during the copy.

Yes, you can auto-trust dev tools like mise and direnv configurations. The process applies branch-aware safety checks to automatically trust these configurations on specific base branches, minimizing prompts during your workflow.

The best way to manage parallel feature development is creating branch-specific git worktrees. This allows you to run multiple isolated environments simultaneously for long-running experiments or PR reviews without disrupting your primary repository.

The .worktrees directory should be ignored by git to prevent your isolated workspaces from being tracked in version control. The setup process ensures this directory is automatically added to your ignore rules to keep your repository clean.

No external dependencies are required to set up an isolated git worktree. The setup relies entirely on built-in scripts to provision the workspace, copy environment files, and apply branch-aware safety rules without needing additional packages.