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

..

delivery.test.ts

Never set warning on the merge check's statuses: the forge blocks a required one

2026-10-07 13:55:34 +02:00

pages.test.ts

gitea: say which changed directories hold a module at the merge commit (hq issue 278)

2026-10-06 19:55:17 +02:00

protection.test.ts

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)

2026-10-06 21:56:04 +02:00

pulls.test.ts

Never set warning on the merge check's statuses: the forge blocks a required one

2026-10-07 13:55:34 +02:00

token.test.ts

Add mesh-delivery, the owner of deliveries and delivery groups (hq ADR 0239)

2026-10-06 23:59:54 +02:00