-
-
Notifications
You must be signed in to change notification settings - Fork 30.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gh-126081: For PRs labeled with "type-feature", require a core review #126082
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🙈 I'm sure it's fine....
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Checking what request-changes looks like)
When you're done making the requested changes, leave the comment: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add some inline comments to explain more clearly what each step does?
For example the "Check for type-feature" seem to only be used for the awaiting-merge check, whereas the "no required changes" can fail the build directly.
4ef698f
to
cb43754
Compare
I have made the requested changes; please review again. |
Thanks for making the requested changes! @hugovk: please review the changes made to this pull request. |
This PR is the test for this PR.