Git Worktree
A Git Worktree is another folder linked to one repository. It lets several branches stay open at once.
Another example
One worktree runs a long feature. Another starts from main and safely patches an urgent production bug.
Main parts
- 01Branch or change set
- 02Review and verification gate
- 03Released result
Use it when
Use it for parallel branches, separate agent tasks, release fixes, or comparisons needing their own folders.
Do not use it when
Do not nest worktrees, delete folders behind Git, or give independent agents overlapping paths.
Name used in code
git worktree add/list/remove Before you ship
Before publishing, check the exact repository, branch, target, and diff. Keep unpublished work. Pass review and CI checks. Record conflict and data-loss risks, release order, traceability, recovery, and rollback.
Outcome: Use Git Worktree to release or recover the change safely, with a clear record. User context: One worktree runs a long feature. Another starts from main and safely patches an urgent production bug. Delivery concept or operation: Git Worktree. Why it fits: Use it for parallel branches, separate agent tasks, release fixes, or comparisons needing their own folders. Do not use it when: Do not nest worktrees, delete folders behind Git, or give independent agents overlapping paths. Delivery requirements: Name the code repository and target. List preconditions, changes, review and CI checks, conflict and data-loss risks, release order, and the rollback or recovery command. Repository safeguards: Keep unpublished work and a clear history. Do not run destructive steps without an explicit backup. Check the exact code diff and remote target before publishing. Acceptance criteria: Review the intended diff and pass all required checks. Keep the target version traceable. Practice failure recovery and keep published history clear. Evidence and limits (evidence boundary): It is official for that source. Other platforms or teams may use the term in another way. Unknowns to confirm: Repository, branch, team activity, release environment, approval owner, protected checks, and rollback target.
Check this request
Review the current use of Git Worktree. Definition: A Git Worktree is another folder linked to one repository. It lets several branches stay open at once. Release checks: Before publishing, check the exact repository, branch, target, and diff. Keep unpublished work. Pass review and CI checks. Record conflict and data-loss risks, release order, traceability, recovery, and rollback. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.