Step 5 of playbook 08 now runs mesh-controller.try on the pushed branch and opens the pull request only once it passes. A local run never stands in for it: the check's containers carry other tools than the nodes. Seen 2026-10-15 on mesh-catalog #323 (issues 860, 862): a test calling util-linux flock -E passed on a node and failed on BusyBox's flock in the check, costing a review round.
A playbook edit of a few lines: the operator's word on this pull request is its review (playbook 08 step 4). hq's merge-check.sh passes locally.
Step 5 of playbook 08 now runs `mesh-controller.try` on the pushed branch and opens the pull request only once it passes. A local run never stands in for it: the check's containers carry other tools than the nodes. Seen 2026-10-15 on mesh-catalog #323 (issues 860, 862): a test calling util-linux `flock -E` passed on a node and failed on BusyBox's flock in the check, costing a review round.
A playbook edit of a few lines: the operator's word on this pull request is its review (playbook 08 step 4). hq's merge-check.sh passes locally.
Deliverynovox/hq@ba7c9e7f1765 — proposed since 2026-10-15T23:52:51Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-15 21:33 (new) → proposed (announced): novox/hq#369's head announced
2026-10-15 21:34 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-15 21:34 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-15 23:52 ready → proposed (trunk moved): out of date: judged against trunk 9bfd57174f, the trunk is now f8c0676b3a1d; judged again on a recheck or when it is merged
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/hq@ba7c9e7f1765` — **proposed** since 2026-10-15T23:52:51Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-15 21:33 (new) → proposed (announced): novox/hq#369's head announced
- 2026-10-15 21:34 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-15 21:34 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-15 23:52 ready → proposed (trunk moved): out of date: judged against trunk 9bfd57174fab, the trunk is now f8c0676b3a1d; judged again on a recheck or when it is merged
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.
Step 5 of playbook 08 now runs
mesh-controller.tryon the pushed branch and opens the pull request only once it passes. A local run never stands in for it: the check's containers carry other tools than the nodes. Seen 2026-10-15 on mesh-catalog #323 (issues 860, 862): a test calling util-linuxflock -Epassed on a node and failed on BusyBox's flock in the check, costing a review round.A playbook edit of a few lines: the operator's word on this pull request is its review (playbook 08 step 4). hq's merge-check.sh passes locally.
Delivery
novox/hq@ba7c9e7f1765— proposed since 2026-10-15T23:52:51ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
9bfd57174f, the trunk is now f8c0676b3a1d; judged again on a recheck or when it is mergedThe commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.