[thekevinbot]

⚠️ This will need an admin merge. The gate it reverts deadlocks every PR, including this one.

#check-pending = 0 deadlocks merge protections, exactly as the comment #945 removed said it would. Confirmed on #946 — after all 91 checks completed, Mergify sat pending:

🟠 All CI green — Waiting for:  [ ] #check-pending = 0
    Waiting checks: ``.          ← empty
                    [X] #check-failure = 0

The "waiting checks" list is empty. The only pending check is Mergify's own, which it cannot name, so the count never reaches zero.

My evidence for doubting the original comment (discussion #2184, the pending-events changelog) described pull_request_rules, where Mergify produces no check of its own. It does not carry over to merge_protections.

Restores the previous behaviour, including its known defect: the gate is vacuously green before CI starts (#943, reopened). The remaining fix is pr-monitor — Option B — not a condition tweak.

E2E Verification

N/A - CI configuration only

---

[thekevinbot]

Superseded by #950, which deletes .mergify.yml entirely — no point reverting one rule inside a file that's going away. The deadlock this documented (#check-pending = 0 counting Mergify's own check, so it never reaches zero) is real and worth keeping in the record; the fix is dropping Mergify, not tuning it.