mesh-delivery: a closed pull request's check builds go, and a walk says what each build did (ADR 0350, issue 649) #282

Merged

mesh-admin merged 1 commits from feat/350-one-build-per-change into main

2026-10-13 21:30:30 +00:00

Author	SHA1	Message	Date
jschoubben	66d22dd53e	Let a closed pull request's check builds go, and show what each walk build did mesh/merge-gate head 66d22dd53eff merged into trunk 7ed119995f69 — pass: builds mesh-delivery → novox; no bus step; every machine composes with the change … Details mesh/repo-check head 66d22dd53eff merged into trunk 7ed119995f69 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-… Details mesh/delivery delivered Details mesh/delivery-group group feat/350-one-build-per-change delivered: every member is delivered Details A check's builds for its merge have no taker once the pull request closes unmerged, and the delivery should say whether a module was reused from the check or built, and why (novox/hq ADR 0350 §4, §5).	2026-10-13 23:04:41 +02:00