Repository navigation
ci: share Ready checks and guarded automatic merge - #10
Merged
Merged
Conversation
added 4 commits
October 14, 2026 19:03
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.
Ready PRs need one consistent release policy across the organization. Add reusable repository checks and a metadata-only Ready workflow that requires current-revision CodeRabbit approval when selected and enables normal auto-merge only after a real successful Check and active central requirements.
Drafts stay unpublished. Repository-specific Netlify previews remain centrally required; production keeps scoped check and build.
Validation: ten behavioral tests pass for drafts, skipped checks, stale and missing reviews, requested changes, rollout prerequisites and changed revisions. Independent review is in progress.