Repository navigation
ci: replace owner reviews with automated risk gates - #54
Merged
Merged
Conversation
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.
What changed
Replace this governance job's CODEOWNERS-required review with the automated
risk-gatestatus. High-risk paths need the owner-addedowner-approvedlabel; low-risk paths pass automatically. Existing checks and earlier protections remain in place.The trusted base-branch workflow reads metadata only, checks renamed paths and label provenance, and publishes
risk-gateandpr-templateon the exact PR head. It does not check out PR code, add approval labels, merge PRs, access secrets, or deploy.AI assistance
Codex. No independent AI review result is claimed.
How verified
The generated workflow passed actionlint and JavaScript syntax checks; 27 focused regression cases passed, including low/high risk, owner-label provenance/removal, renames, incomplete diffs and API failures. The repository's existing hygiene/style checker passed where available. GitHub CI and existing merge requirements must pass before merge. Installation uses the existing governance PR process before the new trusted workflow is made required.