docs(ci): the status-check rule was seen blocking a merge - #184
Merged
Conversation
…hat is not The page recorded require-status-check as "configured, not proven". PR #183 is a stronger datapoint than that and it should be written down: while build-test (windows-latest) was still running, mergeStateStatus was BLOCKED against mergeable: MERGEABLE, and it flipped to CLEAN the moment that job finished. The rule is load-bearing, not a setting that saved and did nothing. But it is a stronger datapoint, not the proof. What was observed is that a PENDING required check blocks. The case this rule exists for is a FAILING one, and GitHub could treat a concluded failure differently from a not-yet-reported check. Recording the distinction rather than rounding it up, because rounding it up is how a gate gets trusted for something it does not do -- the same failure mode as the force-push row two sections down, which is honest about never having been tested. Closed cheaply by noticing the next real CI failure; not worth manufacturing one.
Nghaiz
force-pushed
the
docs/branch-protection-observed
branch
from
August 25, 2026 10:43
f2607e1 to
532e717
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR #183 was the first thing the new
required_status_checksrule applied to, and it behaved: whilebuild-test (windows-latest)was still running,mergeStateStatuswas BLOCKED againstmergeable: MERGEABLE, flipping to CLEAN the moment the job finished.That is worth recording, and so is what it is not. It shows a pending required check blocks. The case the rule exists for is a failing one, and those are not the same event — GitHub could treat a concluded failure differently from a not-yet-reported check. The page now says strongly indicated, not proven, and points at the cheap way to close it: notice the next genuine CI failure rather than manufacture one.
Same discipline the force-push row two sections down already uses.