chore: correct develop ruleset to match what the API accepts#11
Merged
Conversation
The first version failed against the rulesets API: - the GitHub Actions Integration bypass actor is rejected on user-owned repos (must be added via the UI instead) - `automatic_copilot_code_review_enabled` is not a valid pull_request param Removes both; documents the one-time UI step for the GitHub Actions bypass. This matches the active `protect-develop` ruleset.
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.
Corrects
scripts/develop-ruleset.json+ applier to match theprotect-developruleset that is now live on this (public) repo.Two things the rulesets API rejected in the original version:
automatic_copilot_code_review_enabled— not a validpull_requestparameter. Removed.The applier was already run; this just makes the tracked files reproducible and accurate.