3 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	d2036f2a63	gitea: require no status on main, judge mesh/check in the merge tool instead (ADR 0534) ... The forge's required status was a second copy of the gate mesh-delivery and the merge tool already keep; a stuck status writer held it too (issues 1886, 1891) and only a hand change at the forge let a fix merge. Main keeps no push, the tools' merge whitelist and no administrator override. The merge tool judges mesh/check whether or not the branch requires it, and on a branch that requires none merges only a head the operator's Approve names. The protection tool loses its status argument.	2026-10-23 12:01:57 +02:00
jschoubben	5e24deb0f1	gitea: require mesh/check in place of the two old statuses on every main the gate judges (issue 1301, S1-S3) ... ADR 0447 §1 has main require mesh/check alone. The repositories program now requires it in place of mesh/merge-gate and mesh/repo-check on every listed repository and on every other one whose main requires mesh/merge-gate, so the switch needs no hand-kept list (lead decisions L4, L11). A main requiring mesh/repo-check alone (hq) keeps it until issue 1296 (ADR 0503 §5).	2026-10-22 17:49:53 +02:00
jschoubben	54db38be08	gitea: a repository the module makes refuses an administrator's merge past its checks (issue 1141) ... narrowed never set block_admin_merge_override, so novox/mesh-delivery's main let an administrator merge past mesh/merge-gate and mesh/repo-check, unlike every other repository's main since 2026-10-07. narrowed sets it and isRight requires it, so the module's next start puts mesh-delivery right.	2026-10-18 18:10:29 +02:00