feat(policy): reconcile explicit advisory CI delivery intent - #77
Merged
Conversation
Signed-off-by: rldyourmnd <danil@nddev.it.com>
Signed-off-by: rldyourmnd <danil@nddev.it.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.
Selecting the optional
continuous-developmentpolicy makes broad CI asynchronous in generated guidance and projects explicit removal of required status checks from the selected repository ruleset. Omitted rules previously meant preservation in the HTTP writer but deletion in the handler's expected postcondition; both paths now preserve omissions and remove checks only with explicit plan intent.The compiled-policy digest binds the selection. Schema and handler reject contradictory removal/check declarations and empty creation. Existing checks-only rulesets can become explicitly empty, exact readback detects restored checks, and replay avoids another write. Other rules, conditions and bypass actors are preserved; ordinary updates retain unknown status-check parameters. Defaults remain unchanged. This does not activate profiles, mutate live settings, implement application deployment, or remove other GitHub gates.
Validation: complete
scripts/validate_go_core.sh --quickon Go 1.26.7 (full Go tests/vet, schemas, projections, build);-racefor compiler/projections/provider/handler/app/validation; 47 Python tests. Golden fixtures regenerated through their generator. Native projection plan/apply/verify and repeated generation check passed, operationop_01M1X2J80DAVHX0K40X774PD0P.Closes #76.