Answer what the mesh's checks said of a pull request, as mesh-delivery's checks verb (hq ADR 0239)
mesh/delivery-group group feat/delivery-checks-verb delivering: 0 of 2 delivered
mesh/merge-gate pass: builds gitea, mesh-delivery → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery superseded: a newer delivery to the same trunk took over its walk

Reading a pull request's mesh/merge-gate and mesh/repo-check meant scraping the controller's journal:
the forge clips each status to 140 characters and nothing returned the verdict whole. mesh-delivery
already keeps the verdict; it now keeps the machine that ran it, the layers' modules and the report,
and its checks verb joins that to the forge's statuses, read through a new gitea_commit_statuses tool
that also says whether the base's protection lets the commit merge.

after: novox/mesh-controller
This commit is contained in:
jochen
2026-10-07 19:36:41 +02:00
parent c74f407abd
commit 13894744a7
14 changed files with 919 additions and 15 deletions
+3 -1
View File
@@ -11,6 +11,7 @@
"show",
"groups",
"what-if",
"checks",
"table",
"stalled",
"recheck",
@@ -40,7 +41,8 @@
"seat:mesh-controller.delivery-walks",
"gitea.gitea_note_append",
"gitea.gitea_delivery_view",
"gitea.gitea_commit_status"
"gitea.gitea_commit_status",
"gitea.gitea_commit_statuses"
],
"state": [
"deliveries",