Summary
We use .jarvis/worktrees/ for isolated per-task git worktrees (see JARVIS_WORKTREE_ROOT in CLAUDE.md), but there is no standalone doc explaining the convention for contributors.
Request
Add a new file docs/worktrees.md with a short explanation:
- What
.jarvis/worktrees/ is used for (isolated worktrees for parallel/automated work).
- That the directory is gitignored (
.jarvis in .gitignore).
- The branch naming convention
fix/issue-<n> used by automated fixers.
- How to list and clean them up (
git worktree list, git worktree remove).
Keep it concise (~20-30 lines). Documentation-only change; no code impact.
(This is a TEST issue used to trial the fix-github-issues workflow. Safe to close afterward.)
Summary
We use
.jarvis/worktrees/for isolated per-task git worktrees (seeJARVIS_WORKTREE_ROOTin CLAUDE.md), but there is no standalone doc explaining the convention for contributors.Request
Add a new file
docs/worktrees.mdwith a short explanation:.jarvis/worktrees/is used for (isolated worktrees for parallel/automated work)..jarvisin.gitignore).fix/issue-<n>used by automated fixers.git worktree list,git worktree remove).Keep it concise (~20-30 lines). Documentation-only change; no code impact.
(This is a TEST issue used to trial the
fix-github-issuesworkflow. Safe to close afterward.)