Automatically assign reviewers on pull request creation #362
Replies: 1 comment
-
This idea is to get things going, not a fleshed out solution. IMO we should create a According to the documentation of the One thing to remember quoting the documentation:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the idea
We should automatically assign reviewers when a pull request gets created. At least in the Xserver repository.
The selection of the appropriate reviewers could be based on the path and/or extension of the source file. This is made possible by creating a
CODEOWNERS
file at the root of a repository. Also the selection could be based on some automatice rules defined at the organization and team level. We could also limit who is allowed to approve or request changes to a pull request.An important note: "The people you choose as code owners must have write permissions for the repository", says the Github documentation. This can be generalized: Anyone who should be assignable as a reviewer needs write permissions for the repository.
It should be done because
Manually assigning reviewers to newly created pull requests is both tedious and errorprone. Without automation the devs have to manually select the reviews on a per pull request basis. Also any other contributor is not able to assign any reviewers, even not the core team ones so there may be no reviewers assigned after all and no notifications send etc. which can lead to stale pull requests.
When manually assigning reviewers one also has to know who reviews what and apply this knowledge to every new pull request. That way, essential reviewers might be forgotten. Also there may be no reviewers assigned at all as this is the Github default.
We should automatically assign the reviewers to get rid of the above mentioned shortcomings.
What are the alternatives?
Keep the status quo, but what for?
Additional context
This feature has been requested in various comments of pull requests when the (missing) workflow stood in the way of the ones working on the pull requests.
@X11Libre/wranglers CC
References to consider:
Extra fields
Beta Was this translation helpful? Give feedback.
All reactions