mesh-catalog

Files

T

jochen 74f912e1fb

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)

Details

mesh/repo-check pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

Put the merge check back to pending before a recheck asks it (hq issue 305)

A recheck asks of the head the forge already judged, and the forge keeps
the newest status of each context on it. Nobody reset mesh/merge-gate or
mesh/repo-check, so the old green stood and branch protection would merge
on it while the fresh check ran; rechecked heads did turn red.

mesh-delivery's recheck now asks the forge's holder to set the gate, and
the repository check when the head holds one, to pending ("checking
again: <why>") before it asks the controller; a forge that cannot be told
refuses the recheck whole. The gitea holder takes pending, and only
pending, on the merge check's statuses by hand: no verdict, so issue 293
still holds.

2026-10-08 10:11:26 +02:00

provisioner

A withdrawn consumer keeps its data, in every provider that holds some (hq issue 241)

2026-10-05 00:34:40 +02:00

test

Put the merge check back to pending before a recheck asks it (hq issue 305)

2026-10-08 10:11:26 +02:00

tools

Put the merge check back to pending before a recheck asks it (hq issue 305)

2026-10-08 10:11:26 +02:00

checks.ts

Answer what the mesh's checks said of a pull request, as mesh-delivery's checks verb (hq ADR 0239)