ENH: Auto-assign reviewers to new pull requests
See original GitHub issueDescription
Use https://docs.github.com/en/free-pro-team@latest/github/creating-cloning-and-archiving-repositories/about-code-owners and https://www.astropy.org/team (which is rendered from roles.json) to auto-assign reviewer(s) for new pull requests on this repo.
This file must not be in the root directory, but rather in .github
sub-directory.
cc @astropy/devops-maintainers
Additional context
astropy/astropy-bot#101
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Gitlab auto-assign reviewer for merge request - Stack Overflow
I've been using GitHub for my previous project, and I had what is called auto-assign reviewer for pull requests that automatically assigns a ......
Read more >Using Cloud Functions to auto-assign reviewers to GitHub pull ...
Assigns a reviewer to the new pull request based on the amount of reviews already assigned to other reviewers for the open pull...
Read more >Auto-assign a user to a merge request (#287636) - GitLab.org
When a user clicks the "Create merge request" button from within an issue, that user will be automatically assigned to the MR.
Read more >Auto Assign - Probot
Auto Assign adds reviewers/assignees to pull requests when pull requests are opened. How it works. When the pull request is opened, automatically add...
Read more >Stacked changes: how FB and Google engineers stay ...
Auto-assign reviewers from a review group, allowing shared ... to shoehorn into pull requests, and just did what people do with Phabricator, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That is fine. It is already how CODEOWNERS work.
IMO this hypothetical auto-assigner should only trigger on non-draft PRs (and therefore when they switch from draft to ready-for-review). Edit: I see @taldcroft had similar thoughts.