pub const CHECKS_GRACE: Duration;Expand description
How long the checks may stay unreadable before landing gives up on them.
GitHub registers a workflow run some seconds after the branch is pushed, so
immediately after a pull request is opened “no checks” and “no CI in this
repository” look identical. Measured on run 01c2: magi opened pull request
22, read unknown four seconds later, refused to merge on a guess and
marked the run blocked - and every check on that pull request was green
minutes afterwards, with the whole competition then re-run from scratch for
a task that was already finished. Three minutes is well past the observed
registration delay and still bounded, so a repository that genuinely has no
checks costs one three-minute wait and then says so.