Reviewer assignment selects people or groups for a pull request. Automating that choice reduces repeated effort and bias while supporting code review as knowledge transfer; the right level depends on team size and structure. section 5.4.3
Choose an arrangement that matches the team:
- Assign the whole team automatically for a simple default. This suits smaller teams and makes every change broadly visible, but can become noisy for teams of roughly eight or more people. section 5.4.3
- Create groups such as Always Required, Informational, frontend, backend, or technology-specific teams. Groups narrow assignments and help newcomers understand expertise and responsibilities. section 5.4.3
- Assign reviewers from changed files and team expertise. File ownership rules can request the relevant people automatically when particular parts of the codebase change. section 5.4.3
A file-based assignment rule
A CODEOWNERS-style file can define global owners, override them for matching patterns, associate Python files with an email address, and assign teams as owners. Because later patterns take precedence, a JSX change can request its specific owner instead of the global owners.
