Skip to content
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

Merged

Conversation

sunjayBhatia
Copy link
Member

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

@sunjayBhatia sunjayBhatia added the release-note/none-required Marks a PR as not requiring a release note. Should only be used for very small changes. label Oct 25, 2023
@sunjayBhatia sunjayBhatia requested a review from a team as a code owner October 25, 2023 18:45
@sunjayBhatia sunjayBhatia requested review from tsaarni, stevesloka and skriss and removed request for a team October 25, 2023 18:45
@sunjayBhatia
Copy link
Member Author

As part of this we might need to disable reviews on the @projectcontour/maintainers team to let this action handle all the reviewer logic

@sunjayBhatia
Copy link
Member Author

Also may want to unset this:

- projectcontour/maintainers

@codecov
Copy link

codecov bot commented Oct 25, 2023

Codecov Report

Merging #5896 (3aaa658) into main (cf8fb1c) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #5896   +/-   ##
=======================================
  Coverage   78.66%   78.66%           
=======================================
  Files         138      138           
  Lines       19670    19670           
=======================================
  Hits        15473    15473           
  Misses       3894     3894           
  Partials      303      303           

@sunjayBhatia
Copy link
Member Author

unfortunately to get access to the secret needed to access teams, had to switch to the pull_request_target event to trigger the workflow on, which then won't run on this PR since the base branch doesn't include the workflow

@sunjayBhatia
Copy link
Member Author

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


options:
ignore_draft: true
number_of_reviewers: 2
Copy link
Member

@skriss skriss Nov 2, 2023

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.

Copy link
Member Author

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

Copy link
Member

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.

Copy link

The Contour project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 14d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the PR is closed

You can:

  • Ensure your PR is passing all CI checks. PRs that are fully green are more likely to be reviewed. If you are having trouble with CI checks, reach out to the #contour channel in the Kubernetes Slack workspace.
  • Mark this PR as fresh by commenting or pushing a commit
  • Close this PR
  • Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 17, 2023
@sunjayBhatia sunjayBhatia removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 5, 2023
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>
@sunjayBhatia sunjayBhatia changed the title Use necojackarc/auto-request-review action to request reviews Use necojackarc/auto-request-review action to request reviews from non-maintainers Dec 5, 2023
@sunjayBhatia
Copy link
Member Author

I'll need to regenerate the secret referenced in the workflow as I believe that has expired

@sunjayBhatia
Copy link
Member Author

Ok regenerated token and merging

@sunjayBhatia sunjayBhatia merged commit 9d71639 into projectcontour:main Dec 6, 2023
26 checks passed
@sunjayBhatia sunjayBhatia deleted the use-auto-request-review branch December 6, 2023 18:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-note/none-required Marks a PR as not requiring a release note. Should only be used for very small changes.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants