chore: enforce repository governance and release reliability - #14
Merged
Merged
Conversation
17 tasks
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.
Closes #13
Summary
Establishes repository governance and release reliability controls.
Policy
Required checks
validate (Python 3.10)validate (Python 3.12)Analyze (python)CodeQLEvidence
GOVERNANCE.mdevidence/phase7-governance-release-reliability.mdDA9647533BD4879094977EF159401F0C3AD65CB6B4CEF7310E90241A6158B562247122e00e49a0b3e8c53e19d19c28ac2402d266Repository rulesets are activated only after this PR head passes the required checks; the PR is then merged under the new governance policy.