README: document the merge gate on main (PR-only, required CI, fast-forward-only); check off todo

2026-07-03 14:50:54 +02:00
parent c78770a713
commit 7a3161d3ff
2 changed files with 8 additions and 4 deletions
@@ -1174,6 +1174,12 @@ Gitea Actions (`.gitea/workflows/`) runs the pipeline; the test job runs
 `main` is not re-tested on push — its commits are meant to arrive already green from a
 gated branch, so the status check to gate a merge on is `CI / full-gate (push)`.

+**Merge gate on `main`** (Gitea branch protection + repo merge settings, set via the API —
+no repo files involved): direct pushes are blocked, changes land via PR only, the
+`CI / full-gate (push)` status must be green (admins included), and the only merge style is
+**fast-forward-only** — history stays linear and `main`'s head is the exact commit hash of
+the merged branch, which is why the branch's push-triggered status carries over.
+
 **One-time server setup** — register an
 [act_runner](https://docs.gitea.com/usage/actions/act-runner) in host mode with the label
 `docker-host` (config: `labels: ["docker-host:host"]`) on a machine with Docker Engine +