novox/mesh-catalog

Merge a pull request marked ready at its head once its checks pass (issue 722) #303

Merged

mesh-admin merged 3 commits from feat/merge-on-ready into main

2026-10-14 19:57:01 +00:00

Author	SHA1	Message	Date
jschoubben	baa5ef802e	Name the keys gitea's mergeable config takes: none (ADR 0326) mesh/merge-gate head baa5ef802e82 merged into trunk 7e3e62062bef — pass: builds gitea, mesh-delivery → novox; no bus step; every machine composes with the … Details mesh/repo-check head baa5ef802e82 merged into trunk 7e3e62062bef — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-… Details mesh/delivery delivered Details gitea now declares a setting, so every mergeable file of it must name its keys; the runtime config reads no setting, and ready-authors reaches its own file.	2026-10-14 21:50:05 +02:00
jschoubben	5b20e419ec	Count a ready mark only from a listed account, after the last push and the label (issue 722) mesh/merge-gate head 5b20e419ec1f merged into trunk 7e3e62062bef — fail: builds gitea, mesh-delivery → novox; no bus step; a manifest the change touches fa… Details mesh/repo-check head 5b20e419ec1f merged into trunk 7e3e62062bef — fail: its merge-check.sh failed: files asking for a setting without saying whether it is… Details mesh/delivery superseded: a newer head of the same pull request Details Review of #303: anyone who can comment could turn a stale label into a mark, and a long thread hid the newest comment. The forge now reads the pull request's whole timeline and takes a "ready at" comment only from the accounts in the trusted setting ready-authors (default the mesh's own forge account and the operator's), written after the label was last added and after the last push; any other author is ignored and said in the log.	2026-10-14 21:45:39 +02:00
jschoubben	7e0001e304	Merge a pull request marked ready at its head once its checks pass (issue 722) mesh/merge-gate out of date: judged against trunk 482232e8c51c, the trunk is now 7e3e62062bef; judged again on a recheck or when it is merged Details mesh/repo-check out of date: judged against trunk 482232e8c51c, the trunk is now 7e3e62062bef; judged again on a recheck or when it is merged Details mesh/delivery superseded: a newer head of the same pull request Details The operator wants a reviewed pull request merged without a session calling the merge tool again after every recheck. The reviewer marks it ready (label mesh/ready and a comment "ready at <full head sha>"); the forge's open-pulls read carries the mark, and mesh-delivery merges through gitea_merge_pull_request at that head, in a group's order once its composed check passed. A push after the mark clears it; a failed check is said on the pull request and as a stalled line.	2026-10-14 21:23:26 +02:00