docs: mergeable is a plain bool, not a tri-state on the wire

2026-09-26 20:48:31 +10:00
parent 54c1d868d3
commit 7baa194c52
2 changed files with 21 additions and 5 deletions
@@ -88,7 +88,13 @@ gets a **new comment from someone other than the agent**, its **CI fails**
 transitions — CI `pending`→`success`, the agent's own comments and pushes — are
 ignored, and so is any condition the PR was already in at the baseline: a PR
 that is already conflicted or already failing when watching starts keeps being
-watched.
+watched, and the baseline line says which conditions it is staying silent about.
+
+Gitea reports `mergeable: false` both for a real conflict and while it
+recomputes the merge base after a push, so a conflict is only reported once the
+watch has seen a merge computation start — the PR was mergeable, or its head or
+base commit moved — and then only across two consecutive polls of an unchanged
+head and base.

 ```bash
 # Watch until something meaningful happens (default interval 60s)