Suggest GitHub labels and reviewers from changed paths
Use the repository's Automation settings to route pull requests by changed files and inspect what the review did with the matching rules.
Suggest labels and reviewers#
A repository's Settings → Automation page can suggest GitHub labels and reviewers for each pull request.
Under Path labels, choose Suggest and select Add path label. Enter an existing repository Label and its Path globs, one per line, then select Save path labels. When a pull request opens, Proofline records each label whose globs match a changed file. The review page lists them under Suggested labels with the paths that matched. Proofline never applies a label, so add it on GitHub.
Under Reviewer routing, choose a Mode:
- Suggest lists the chosen reviewers under Routed reviewers on the review page. Select Request these reviewers there to request them on GitHub.
- Apply requests them on GitHub. Proofline requests each person once per pull request, so a reviewer someone removed stays removed.
Then set Reviewers to choose to One or Two, and Skip people with this many open review requests to a number from 1 to 50. Optionally choose a Security team, a candidate when a change touches security-sensitive paths. Select Save reviewer routing.
Proofline chooses reviewers when a pull request opens, reopens or leaves draft. Candidates are the CODEOWNERS owners of the changed files, read at the pull request's base, and the recent commit authors of those files. Proofline never chooses the pull request's author or a bot, and it chooses only people and teams with write access. If GitHub lists only part of the changed files, the review page says that no labels or reviewers were chosen. An unreadable CODEOWNERS file at the base also stops reviewer routing for that pull request.