novox/hq
13
0
Fork 0
Code Issues Pull Requests 1 Releases Wiki Activity

Playbook 07: one milestone is one branch per repository, its steps reuse the name (the operator, 2026-10-17)
mesh/merge-gate head edff1f25a10b merged into trunk 4325467b4d59 — pass: the change touches no module of the mesh's graph
Details
mesh/repo-check head edff1f25a10b merged into trunk 4325467b4d59 — pass: its merge-check.sh passed
Details
mesh/delivery delivered
Details

Browse Source
This commit is contained in:
jschoubben
2026-10-17 12:04:37 +02:00
parent 85f0aecf5a
commit edff1f25a1
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
00-META/process/07-feature-branches.md
+4 -1
View File
@@ -55,7 +55,10 @@ never into the running one, unless it blocks the running one.
## Phase 0 — Prepare (the lead, larger model)
1. **Name the feature once:** `feat/<slug>`, the same branch name in every repository it touches. The
branch is never protected.
branch is never protected. **One milestone is one branch per repository** (the operator, 2026-10-17): every
step of a milestone uses the milestone's one name and its one folder `.work/<slug>/`; after a step's merge,
which removes the branch on the forge, the next step makes it again from the new `main` under the same name.
Never a second name for a step (`-2`, `-step2`).
2. **Make the worktrees:** one per touched repository under `.work/<slug>/<repo>`, branched off `main`
(`git worktree add .work/<slug>/<repo> -b feat/<slug> origin/main`). The lab beds find the other
repositories by sibling path, so add the untouched siblings the lab reads as detached worktrees on