Awesome Reviewers

Verification · Code review · Reviewer routing

Path ownership

Route by file path ownership rules.

How to build it

  1. List the owners of each top-level directory in CODEOWNERS.
  2. Require review from a listed owner for changes to owned paths.
  3. Update the file when a team or directory changes owner.

Signals in a repository

  • A CODEOWNERS file at the repository root or under .github.
  • Branch protection rules that require code owner review.
  • Review requests on pull requests that name a team for a path.

In practice

No scanned repository runs a tool for this check. The steps above are the only guidance.