Skip to content

Ruleset 23787415 requires 'SonarCloud Code Analysis', which no PR ever receives (SonarCloud parked, #443) #1081

Description

@hyperpolymath

Finding

Ruleset 23787415 ("main gate: append-only + required checks + signatures + scanning") lists SonarCloud Code Analysis as a required status context on main. None of the five pull requests checked received that context — #1067, #1076, #1077, #1078 (open) and #1064 (merged 2026-09-29). The SonarCloud rollout is parked (#443), so nothing emits it.

A required context that nothing can emit makes every PR permanently BLOCKED; the only way anything lands is a bypass. That hides every other required check's verdict behind the same bypass, which is the vacuous-gate pattern this repo's own doctrine warns about.

Found by the new squabble verify-satisfied (cicd-squabbler, stacked on #114), which reports it on #1076 as required check 'SonarCloud Code Analysis' is Missing. Confirmed independently via gh pr view N --json statusCheckRollup (zero sonar entries on all five PRs).

Acceptance criteria

  • Either SonarCloud is wired for hyperpolymath/standards so a PR's head receives a SonarCloud Code Analysis context, or that context is removed from ruleset 23787415's required_status_checks (owner decision — this issue does not presume which).
  • Control: a fresh PR shows the context present (first arm) or rules/branches/main no longer lists it (second arm), and squabble verify-satisfied hyperpolymath/standards <that PR> no longer reports it Missing.
  • If the second arm: Estate campaign: roll SonarCloud across all repos (parked, resume later) #443 gains a line saying re-adding the required context is part of resuming the rollout, so it cannot come back before the producer does.
  • Sweep: list other repos whose rulesets require a context no PR has emitted in the last 30 days (the same class; see also the "greenness and readability are not PR reachability" lesson). Output is a list, not fixes.

Related: #443 (SonarCloud rollout, parked). Separately, governance / Debt ratchet is red on main since #1064 — that one is being cured by #1078.

🤖 Generated with Claude Code

https://claude.ai/code/session_0136eszqrQ53Kj7aBH1D4rXK

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority:p1High - schedule nextscope:estateAffects many or all repos across the estate

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions