feat: Add required_reviewers support to PullRequestRuleParameters (#3806)
#3811
+128
−7
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
Adds support for GitHub's new ruleset feature that allows requiring specific team approvals on pull requests based on file patterns, as announced in the GitHub changelog on November 3, 2025.
Changes
This PR adds three new types to support the
required_reviewersfield in pull request ruleset parameters:RulesetReviewerType: Type-safe string enum for reviewer typesRulesetRequiredReviewer: Contains minimum approvals, file patterns, and reviewer detailsRulesetReviewer: Nested struct with reviewer ID and typeThe implementation follows existing patterns in the codebase (similar to
BypassActorType) and uses pointer types for proper optionality and JSONomitemptysemantics.Testing
"pull_request_with_required_reviewers"that validates JSON marshaling/unmarshalingAdditional Notes
The
required_reviewersfield is not yet documented in GitHub's OpenAPI schema but is confirmed working in production as of the November 3, 2025 announcement.Resolves #3806
Checklist
script/fmt.shscript/generate.shscript/test.shscript/lint.sh