5 Commits

Include renames

Author	SHA1	Message	Date
jochen	33857626be	Never set warning on the merge check's statuses: the forge blocks a required one ... Branch protection requires mesh/merge-gate (and mesh/repo-check on the core repositories) with no admin override, and the forge combines warning as a failure. A note is now a success that says it; a repository without a merge-check.sh is a success where repo-check is not required and a failure for a person where it is; the status tool refuses the merge check's contexts.	2026-10-07 13:55:34 +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
jochen	9951718623	Check every pull request before it merges, and show the verdict on it (hq ADR 0237, to-be 45 §9) ... The forge's announcer announces each new head of an open pull request as pull.updated, once, and marks the head pending; the controller asks the build seat to check it against every machine of the mesh's facts, and says the verdict as checked, which the forge's holder sets as the head commit's status mesh/merge-gate - an error never as a success - with the check's own account as a comment when it is not a pass. merge-check.sh is the catalogue's check: every manifest through the running controller's module check and merge gate, and the Go tests of each module the change touches, a module whose dependencies cannot be fetched said as not tested.	2026-10-06 21:16:32 +02:00