-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
docs: Don't rely on assignee
filter for reviews
#18676
docs: Don't rely on assignee
filter for reviews
#18676
Conversation
The review-requested:@me filter lists pull requests that expect a review from you or from any team you belong to. To allow everyone to see only pull requests assigned specifically to them, we had to teach MLH to assign individual reviewers to the pull request and then use assignee:@me instead of review-requested:@me. Now that GitHub has a user-review-requested filter, we don't need to rely on the assignee filter anymore for reviews. To view pull requests assigned specifically to you (and not just to one of the teams you belong to), you can use user-review-request:@me. There is one small difference in behavior between the two filters. assignee:@me would display pull requests you already reviewed but gave a Request changes or Comment review. Conversely, user-review-requested:@me will only display pull requests you haven't reviewed yet or for which the author re-requested a review from you. Signed-off-by: Paul Chaignon <paul@cilium.io>
With the introduction of the GitHub filter user-review-requested, we don't need to assign individual reviewers to pull requests anymore. Related: cilium/cilium#18676 Signed-off-by: Paul Chaignon <paul@cilium.io>
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.
Test - 1
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.
Test - 2
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.
Test - 3
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.
Final test
With the introduction of the GitHub filter user-review-requested, we don't need to assign individual reviewers to pull requests anymore. Related: cilium/cilium#18676 Signed-off-by: Paul Chaignon <paul@cilium.io>
With the introduction of the GitHub filter user-review-requested, we don't need to assign individual reviewers to pull requests anymore. Related: cilium/cilium#18676 Signed-off-by: Paul Chaignon <paul@cilium.io>
The
review-requested:@me
filter lists pull requests that expect a review from you or from any team you belong to. To allow everyone to see only pull requests assigned specifically to them, we had to teach MLH to assign individual reviewers to the pull request and then useassignee:@me
instead ofreview-requested:@me
.Now that GitHub has a
user-review-requested
filter, we don't need to rely on the assignee filter anymore for reviews. To view pull requests assigned specifically to you (and not just to one of the teams you belong to), you can useuser-review-request:@me
.There is one small difference in behavior between the two filters.
assignee:@me
would display pull requests you already reviewed but gave aRequest changes
orComment
review. Conversely,user-review-requested:@me
will only display pull requests you haven't reviewed yet or for which the author re-requested a review from you.