MergeGates counts "no statuses on the head" as an unmet gate. A
repository with require_checks on and no .gitbay/ci.yml therefore has
no mergeable merge request and no remedy but turning the setting off.
krz/hypo!1 is the case: no builds have ever run there.
#172 fixed the neighbouring case — a job whose path filters exclude the
push now records a skipped status. Nothing records anything when there
are no jobs at all.
The gate should refuse silence only from a head whose CI would have
spoken: a .gitbay/ci.yml with at least one job that is neither
schedule:- nor tags:-only.
referenced in commit 44533deae4 by cmc: control: a repository that has reported before still waits
2026-09-13 06:57 UTC