Playbook 07: one milestone is one branch per repository #395

2026-10-17T10:04:42Z

mesh-tools commented

2026-10-17 10:04:42 +00:00

The operator, 2026-10-17: "we try to create as least branches as possible, 1 milestone means 1 branch per repo". Phase 0 step 1 now says every step of a milestone uses the milestone's one branch name and folder; after a step's merge removes the branch on the forge, the next step makes it again from main under the same name; never a second name for a step. A playbook edit of a few lines (playbook 08: the operator's word is its review).

mesh-tools added 1 commit 2026-10-17 10:04:42 +00:00

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

edff1f25a1

mesh-tools commented

2026-10-17 10:04:52 +00:00

Delivery novox/hq@edff1f25a10b — delivered since 2026-10-17T10:20:36Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

2026-10-17 10:04 (new) → proposed (announced): novox/hq#395's head announced
2026-10-17 10:05 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-17 10:05 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-17 10:19 ready → proposed (trunk moved): out of date: judged against trunk 85f0aecf5a, the trunk is now 4325467b4d59; judged again on a recheck or when it is merged
2026-10-17 10:20 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-17 10:20 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-17 10:20 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-17 10:20 published → delivered (done): nothing for a walk to move

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/hq@edff1f25a10b` — **delivered** since 2026-10-17T10:20:36Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-17 10:04 (new) → proposed (announced): novox/hq#395's head announced - 2026-10-17 10:05 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-17 10:05 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-17 10:19 ready → proposed (trunk moved): out of date: judged against trunk 85f0aecf5ad6, the trunk is now 4325467b4d59; judged again on a recheck or when it is merged - 2026-10-17 10:20 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-17 10:20 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-17 10:20 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-17 10:20 published → delivered (done): nothing for a walk to move The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

jschoubben added the mesh/ready label 2026-10-17 10:05:15 +00:00

jschoubben commented

2026-10-17 10:05:39 +00:00

ready at edff1f25a1

ready at edff1f25a10b9e72cfa10a07abc55861f1193221

mesh-tools merged commit c61f01d63e into main

2026-10-17 10:20:34 +00:00

mesh-tools deleted branch fix/pb07-one-branch-per-milestone

2026-10-17 10:20:34 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#395