Here's an example of a
reviewpad.yml configuration that label pull requests authored by a member of a group of developers.
Suppose that, as Spotify, you consider developers new joiner until they create/merge their 10th PR. Each time a new joiner creates a PR, you want to label it in order to be able to perform a dedicated code review process. Using Reviewpad groups you can easily do such labeling.
api-version: reviewpad.com/v3.x labels: new-joiner: description: Pull requests created by new joiners # color is the hexadecimal color code for the label, without the leading #. color: "294b69" groups: - name: newJoiners description: Group of developers that have created less than 10 PRs kind: developers type: filter param: developer where: $totalCreatedPullRequests($developer) < 10 rules: - name: authoredByNewJoiner kind: patch description: Patch authored by new joiner spec: $isElementOf($author(), $group("newJoiners")) workflows: - name: critical description: Modifications by new joiners require careful review if: - rule: authoredByNewJoiner then: - $addLabel("new-joiner")
Updated 14 days ago