docs(governance): owner-action checklist (Tier 2)#41
Merged
Conversation
The in-repo gates and audits (including audit_supply_chain) enforce most of the quality bar, but four protections can only be set in GitHub settings: required status checks (Quality gates + Secret scanning), a release-PR token, the Code Quality org preview, and v* tag protection. Consolidates these into a canonical docs/repository-governance.md, with the current ruleset state verified against the live API (PR + CodeQL code_quality + no-deletion + non-fast-forward are enforced; there is no required_status_checks rule and no tag ruleset). Linked from the README so an adopter can audit governance against reality. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Code Coverage OverviewLanguages: Python Python / code-coverage/pytestThe overall coverage remains at 89%, unchanged from the branch. Code Coverage is in Public Preview. Learn more and provide us with your feedback. |
jimCresswell
added a commit
that referenced
this pull request
Jun 18, 2026
…ns (#42) The "highest proportionate bar" program is finished and v0.3.0 is cut. Refresh the continuity entry point and the gate-expansion thread record to reflect F6 (#37), Tier 3 (#38/#39/#40), Tier 2 (#41), Dependabot (#29/#30) and the release, and to list the owner-only settings and the documented F6 residuals as the only remaining work. Napkin captures the load-bearing lesson: a safety guardrail must prefer over-blocking to under-blocking — the reverted heredoc-strip would have let a bash-fed quoted heredoc force-push slip, because a quoted delimiter blocks expansion, not execution. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.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
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.
What & why
Tier 2 (governance write-up). The
audit_supply_chainself-check already landed; this is the remaining deliverable — the owner-action checklist for protections that can only be set in GitHub settings (I cannot change repo/org settings from code).New canonical
docs/repository-governance.mddocuments:mainruleset (verified live via the API): PR required, CodeQLcode_qualityrequired, no branch deletion, no force-push.Quality gates+Secret scanning (gitleaks)to required status checks (biggest gap — there is norequired_status_checksrule today, somaincan go red and still merge).ci.ymlruns on it.v*tag ruleset (none exists today).Linked from the README so an adopter works through it once per repo.
Verification
🤖 Generated with Claude Code