Repository navigation
fix(governance): correct main protection payload [WO-001A] - #6
Open
KayzenRoot wants to merge 6 commits into
Open
KayzenRoot wants to merge 6 commits into
KayzenRoot wants to merge 6 commits into
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.
Summary
Correct the GitHub main-branch protection payload used by
scripts/finalize-execution.ps1. GitHub's current API rejects a nulldismissal_restrictionsobject, so the field is omitted while all requested protections remain enabled.Validation
npm test(10/10)npm run lintnpm run typechecknpm run buildRisk and rollback
This changes only the governance automation payload. Revert commit
aea4e22if needed.Security and data handling
No credentials, environment files, databases, or Review ZIPs are included.
This pull request is intentionally not auto-merged.