gitea: graph-driven announce, both check statuses, the change plan, branch-protection tools (hq ADR 0238) #98

Merged

mesh-admin merged 4 commits from feat/the-graph-decides-what-is-checked into main 2026-10-06 21:00:27 +00:00

Conversation 1 Commits 4 Files Changed 9

+360 -38

4 Commits

Author	SHA1	Message	Date
jochen	81641a4b22	Test the modules the planner says the change reaches (hq ADR 0238)	2026-10-06 22:54:52 +02:00
jochen	cc1305a354	gitea: post a pull request's change plan with its verdict (hq ADR 0238) ... The gate's status says what the change does and how it was judged; a change that builds something gets its plan as a comment — the tiers, what each machine receives, and what is not an ordinary send.	2026-10-06 22:50:32 +02:00
jochen	dba71a97a8	gitea: tell the controller which files a pull request deletes; say the dependents a merge would build (hq ADR 0238) ... The controller asks its planner what a pull request reaches, as if merged: a module whose manifest the change deletes is one the merge removes, and the plan's dependents are said on the gate's status beside the modules it moves.	2026-10-06 22:34:53 +02:00
jochen	bd7b757dd9	gitea: give the controller what it maps a pull request onto the graph with; set both check statuses; protect a branch by tool (hq ADR 0237) ... The controller now decides what a pull request's check runs from the mesh's module graph, so the announcement carries the changed directories that hold a module at the head and whether the head has a merge-check.sh. A verdict sets mesh/merge-gate (the gate, with the modules it judged) and mesh/repo-check (the repository's own tests). gitea_branch_protection_get/set let the operator's agent make those statuses required. The catalogue's merge-check.sh leaves the gate to the build seat and keeps its own layer: every manifest through module check, and the touched Go modules' tests.	2026-10-06 21:56:04 +02:00