# Reviewer pools

> How the rotation picks a reviewer, how many people a pool needs, and how bots are treated.

A reviewer pool is a group of people who review a set of repositories. When a pull request doesn’t already request a reviewer, its repository’s pool picks the next person in turn.

## How the rotation works

-   People take turns, so reviews spread evenly over time rather than landing on whoever answers first.
-   Nobody is asked to review their own pull request.
-   Paused reviewers are skipped until you resume them, for holidays or busy weeks.
-   Nudge requests the chosen person’s review on GitHub or Gitea, so the git host shows the same reviewer.

If the pull request already requests reviewers, Nudge respects that and picks one of them instead. See [Who is accountable](https://nudgepr.dev/docs/how-chasing-works#who).

## How many people a pool needs

One person is enough to be chased. But if your policy reassigns stalled reviews, a pool needs **at least two people who can review**, so there’s someone to hand the review to. With only one, Nudge falls back to telling the people you chose for escalation.

> **Small teams**
>
> If only you and one other person are in a pool, your own pull requests always go to them, and theirs to you. Reassignment then has nowhere to go. Add a third reviewer if you want stalled reviews to move on.

## Bots

GitHub App accounts, the ones whose username ends in `[bot]` such as `dependabot[bot]`, are bots. They can’t review, so Nudge never assigns them, never chases them, and they don’t count as seats. Their pull requests are still chased like anyone else’s.

Ordinary accounts used for automation (sometimes called machine users) are treated like people: they can be in a pool, be assigned and be chased, and they count as seats.

## Pools and billing

Everyone in a reviewer pool is a seat. People who only author pull requests, paused reviewers, bots and dashboard members who don’t review aren’t billed. See [Billing](https://nudgepr.dev/docs/billing).
