Repository navigation
chore(ci): bump governance-reusable pin to standards main - #56
Conversation
The pinned revision carries bugs that make Governance red on every consumer: the Workflow security linter runs update-actions-lock.sh from the CALLER's checkout where it does not exist (exit 127), and Allowlist Preflight runs check-actions-policy.sh with an empty GH_TOKEN (exit 3). Both are fixed on standards main. Witnessed green on hyperpolymath/blocky-writer at this exact SHA: governance run completed/success, 15/15 jobs. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Warning Review limit reachedNext included review available in 58 minutes. View limit detailsLimit details: You’ve used the included review currently available. This review ran on the free tier because your account doesn't have an assigned seat on this organization's plan. Waiting won't change this — ask an organization admin to assign you a seat, then retry. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Free Run ID: 📒 Files selected for processing (1)
Note 🎁 Summarized by CodeRabbit FreeThe PR author is not assigned a seat. If you are a newly provisioned user and your organization has automatic seat assignment enabled, open a new pull request to trigger seat assignment. Otherwise, ask an organization administrator to assign a seat through the team management page at https://app.coderabbit.ai/settings/team-management. Comment |
|
Pinned revision
bd0df9eaofgovernance-reusable.ymlcarries two bugs that make Governance red on every consumer:bash scripts/update-actions-lock.sh --verify-localin the caller's checkout, where the script does not exist — exit 127.check-actions-policy.shwith an emptyGH_TOKEN—ghrefuses, exit 3.Both are cured on
standardsmain (fad242d35291de1898242d6737ba02b74a59a2f2): the verifier is copied into\$RUNNER_TEMP, and the policy step is skipped when no credential is supplied.Witness: verified green on hyperpolymath/blocky-writer#55 at this exact SHA — governance run
completed/success, 15/15 jobs, including the two jobs that were red on that repo's default branch.Judge this PR by the set difference against your own default branch (which governance jobs are newly red), not by overall check colour — unrelated build failures may pre-date it.
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com