Repository navigation
ci(admission): defer draft native builds and document contributor rules - #116
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.
Draft PRs currently start native builds alongside older acceptance runs, and becoming ready does not trigger fresh source validation. Add a separate draft preview so later modules can be reviewed without consuming native runners ahead of the oldest ready PR. Consolidate the agreed contributor rules in AGENTS.md.
Only boolean draft=true selects the non-required CI - draft preview context and skips native jobs. Ready PRs get fresh source checks; merge candidates retain the full twelve-profile matrix and CI - required. Malformed metadata fails conservatively. Existing native commands, caches, limits and branch protection are unchanged. Preview success never establishes merge acceptance; a fresh ready-for-review run at the intended head remains required.
Rules record English Conventional Commits and branch names, ordered root-controlled admission, parallel local work, synchronized bilingual documentation, canonical emitted-page checks, local-only raw evidence and the selected co-located plugin layout. No plugin implementation or lifecycle change is included.
Validation:
No native or performance acceptance is claimed by local policy/documentation tests.