-
Notifications
You must be signed in to change notification settings - Fork 681
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
Use necojackarc/auto-request-review action to request reviews from non-maintainers #5896
Use necojackarc/auto-request-review action to request reviews from non-maintainers #5896
Conversation
As part of this we might need to disable reviews on the @projectcontour/maintainers team to let this action handle all the reviewer logic |
Also may want to unset this: contour/.github/dependabot.yml Line 17 in 6917d85
|
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #5896 +/- ##
=======================================
Coverage 78.66% 78.66%
=======================================
Files 138 138
Lines 19670 19670
=======================================
Hits 15473 15473
Misses 3894 3894
Partials 303 303 |
895536b
to
2af7444
Compare
52b8f45
to
8c6dd1e
Compare
8c6dd1e
to
8243354
Compare
unfortunately to get access to the secret needed to access teams, had to switch to the |
we'll likely have to merge this w/o knowing if it works so that PRs have access to the secret/etc. to run this action |
.github/reviewers.yaml
Outdated
|
||
options: | ||
ignore_draft: true | ||
number_of_reviewers: 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.
Is there any way to ensure that at least one maintainer is selected?
Alternately, we could continue with the CODEOWNERS approach for adding maintainers as reviewers, and use this workflow solely for assigning (non-maintainer) reviewers.
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.
ah yeah there might be a way to do so with the "groups" feature, but it might be simpler to keep the CODEOWNERS and just specify reviewers with this action
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.
Circling back here, I'm in favor of keeping CODEOWNERS for existing maintainers, and using this workflow for assigning non-maintainer reviewers.
The Contour project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to the #contour channel in the Kubernetes Slack |
CODEOWNERS only allows requesting reviews from users/teams with owner permission on the repo Use this action which should not require the reviewers github team to have owner permissions Signed-off-by: Sunjay Bhatia <sunjayb@vmware.com>
Signed-off-by: Sunjay Bhatia <sunjayb@vmware.com>
Signed-off-by: Sunjay Bhatia <sunjayb@vmware.com>
Signed-off-by: Sunjay Bhatia <sunjayb@vmware.com>
We'll use CODEOWNERS to request maintainer reviews Signed-off-by: Sunjay Bhatia <sunjayb@vmware.com>
ccf6d55
to
3aaa658
Compare
I'll need to regenerate the secret referenced in the workflow as I believe that has expired |
Ok regenerated token and merging |
CODEOWNERS only allows requesting reviews from users/teams with owner permission on the repo
Use this action which should not require the reviewers github team to have owner permissions