The reviewer marks a pull request ready with mesh-delivery.mark-ready, which writes the label and then the ready at comment in the order the forge counts, instead of two raw forge calls. Group feat/913-mark-ready with mesh-controller and mesh-catalog. hq checks green; reviewed with the group.
The reviewer marks a pull request ready with `mesh-delivery.mark-ready`, which writes the label and then the `ready at` comment in the order the forge counts, instead of two raw forge calls. Group `feat/913-mark-ready` with mesh-controller and mesh-catalog. hq checks green; reviewed with the group.
mesh/merge-gate head 7b5f3582be90 merged into trunk 6dcfa2226e63 beside mesh-controller#357@114c99e0 +1 more — pass: the change touches no module of the me…
composed together: pass — every machine composes with the change as it did without (3 of 4 compose)
Transitions
2026-10-16 12:37 (new) → proposed (announced): novox/hq#383's head announced
2026-10-16 12:45 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-16 12:45 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-16 13:47 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-16 13:47 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.
<!-- mesh-delivery:view -->
**Delivery** `novox/hq@7b5f3582be90` — **delivered** since 2026-10-16T13:47:17Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Group** `feat/913-mark-ready`, in order: novox/hq@7b5f3582be90 → novox/mesh-controller@114c99e02a52 → novox/mesh-catalog@2d1b20364f9b
- novox/mesh-controller@114c99e02a52 before novox/mesh-catalog@2d1b20364f9b: built by
- composed together: pass — every machine composes with the change as it did without (3 of 4 compose)
**Transitions**
- 2026-10-16 12:37 (new) → proposed (announced): novox/hq#383's head announced
- 2026-10-16 12:45 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-16 12:45 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-16 13:47 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-16 13:47 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`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The reviewer marks a pull request ready with
mesh-delivery.mark-ready, which writes the label and then theready atcomment in the order the forge counts, instead of two raw forge calls. Groupfeat/913-mark-readywith mesh-controller and mesh-catalog. hq checks green; reviewed with the group.Delivery
novox/hq@7b5f3582be90— delivered since 2026-10-16T13:47:17ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Group
feat/913-mark-ready, in order: novox/hq@7b5f3582be → novox/mesh-controller@114c99e02a → novox/mesh-catalog@2d1b20364fTransitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.