3 Commits

Include renames

Author	SHA1	Message	Date
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	8c587d0f00	Let the repositories pass's failed exit be its gate: a run-once step the node-engine runs again until it passes, its stderr naming each refused repository, step and forge answer, instead of a health check of its own (issue 1124, ADR 0428 §6)	2026-10-18 16:52:29 +02:00
jschoubben	df275b3c6e	Make the organisation's repositories from the gitea module's config value, protected under the setup account before they join the organisation, and take the owner argument from gitea_create_repo, since a repository's maker becomes its administrator (issue 1124, ADR 0428)	2026-10-18 16:49:12 +02:00