Skip to main content

​
Worktrees

This repository prefers separate worktrees over stacked unrelated changes in one checkout. That matters for humans and agents:
  • less accidental overlap
  • cleaner review boundaries
  • lower risk of reverting unrelated work
  • easier parallel validation

​
Default pattern

Use one worktree per coherent feature or fix. Example:
The helper creates a sibling worktree directory under ../worktrees by default.

​
When to use a worktree

  • a feature will take more than one commit
  • you want to keep release or docs work isolated from runtime work
  • multiple agents or contributors are working in parallel
  • you need to compare two approaches without polluting the main checkout

​
Rules

  • one branch per worktree
  • one main concern per branch
  • do not mix broad dependency churn into feature branches
  • do not use worktrees to hide unrelated unfinished work in a PR