Pull requests labels are widely used by software developers to communicate required actions.
Out of the box, Reviewpad supports the action of adding labels to pull requests.
Together with the other built-in capabilities, you can automate flexible pull request labelling workflows.
📄️ Label based on author groups
Here's an example of a reviewpad.yml configuration that labels pull requests authored by a member of a group of developers.
📄️ Label based on file paths
Here's an example of a reviewpad.yml configuration that labels pull requests that contain changes to a certain filepath.
📄️ Label critical changes with code pattern
The hasCodePattern built-in allows us to query the code contained in the diff.
📄️ Label critical changes with semantic code annotations
The hasAnnotation built-in can be used to access code annotations in Reviewpad configurations. A key differentiator is that Reviewpad can understand the context of changes allowing for powerful checks.
📄️ Label potential missing changes
It is fairly common that changes in some files imply changes in other files.
📄️ Label when git conflicts
It can be tiresome to open a pull request and realize that it has Git conflicts.
📄️ Label with size
The size of a pull request is a good indicator of how much work is involved in reviewing it.
📄️ Remove label based on file paths
Here's an example of a reviewpad.yml configuration that removes a label from a pull request that contains the proper changes based on the file path.