Repository navigation
refactor(ci): relabel the blocking checks 🔴 — they were badged 🟡 while required - #56
Merged
Merged
Conversation
…e required The gate-tier invariant lint found checks carrying the 🟡 CHECK: prefix that are, in fact, required status checks. The label was lying in the reassuring direction, which is the dangerous one: the taxonomy defines 🟡 as "red is a question, not a stop", so a contributor reads the badge, treats a failure as advisory, and then cannot merge. Relabelled to match reality: 🟡 Check: Governance metadata -> 🔴 Gate: ... 🟡 Check: OpenSSF best-practices -> 🔴 Gate: ... 🟡 Check: Hypatia baseline security scan -> 🔴 Gate: ... (only the ones this repository actually requires; the invariant is per-repo, so the same workflow can legitimately be 🟡 elsewhere.) ENFORCEMENT IS UNCHANGED. This edits the workflow `name:` only. A required status check matches on the CONTEXT, which is the JOB name — so relabelling cannot strand a rule or create a phantom. Nothing starts or stops blocking because of this commit; the board simply stops misdescribing what already blocks. Worth stating why this needed a lint to find. Nobody audits a yellow badge — it reads as "informational" and the eye moves on. The mismatch is only visible by comparing the workflow list against the ruleset, which is exactly the kind of cross-check that decays the moment it is left to attention rather than machinery. Found by scripts/check-gate-tiers.sh (metadatastician/standards#578, #581). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
|
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
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.
The gate-tier invariant lint found checks carrying the
🟡 CHECK:prefix that are, in fact, required status checks.The label was lying in the reassuring direction, which is the dangerous one. The taxonomy defines
🟡as "red is a question, not a stop" — so a contributor reads the badge, treats a failure as advisory, and then cannot merge.Relabelled to match reality (only the ones this repository actually requires — the invariant is per-repo, so the same workflow can legitimately stay
🟡elsewhere):🟡 Check: Governance metadata🔴 Gate: Governance metadata🟡 Check: OpenSSF best-practices🔴 Gate: OpenSSF best-practices🟡 Check: Hypatia baseline security scan🔴 Gate: Hypatia baseline security scanEnforcement is unchanged
This edits the workflow
name:only. A required status check matches on the context, which is the job name — so relabelling cannot strand a rule or create a phantom. Nothing starts or stops blocking because of this commit; the board simply stops misdescribing what already blocks.Why this needed a lint to find
Nobody audits a yellow badge. It reads as informational and the eye moves on. The mismatch is only visible by comparing the workflow list against the ruleset — exactly the kind of cross-check that decays the moment it is left to attention rather than machinery.
That is the case for the invariant existing at all: it caught a class of error that reading the board could not, because the error was in the board.
Found by
scripts/check-gate-tiers.sh— metadatastician/standards#578 (the lint) and #581 (the fix that made it resolve job contexts, without which it could not see this).🤖 Generated with Claude Code