# How chasing works

> One accountable reviewer for every pull request, chased on the same timeline until it’s reviewed.

Nudge makes **one person accountable** for each open pull request’s review, and follows up with that person until it’s reviewed. Everything else serves that rule.

## Who is accountable

1.  **Reviewers requested on the git host come first.** If the pull request already requests reviewers, Nudge picks one of them at random to be accountable, even if they’re not in a reviewer pool.
2.  **Otherwise the pool decides.** The repository’s reviewer pool picks the next person in rotation, and Nudge requests their review on the pull request, so GitHub or Gitea shows the same reviewer.
3.  **Nobody accountable is never a quiet state.** If no pool covers the repository, or nobody in it can review, the channel card says the pull request is unassigned and why.

## The timeline

However the reviewer was chosen, they follow the same nudge policy:

1.  **Assigned**: the reviewer is told straight away.
2.  **First nudge** after the policy’s delay, inside working hours, then **repeats** at the policy’s interval.
3.  **Escalation** when nobody responds after the policy’s number of nudges: Nudge tells the people you chose, or reassigns to the next reviewer in the pool.

The exact timings are on [Nudges and escalation](https://nudgepr.dev/docs/nudges).

## When a review is done

A pull request stops being chased when someone other than the author approves it or requests changes, or when it’s merged or closed. After a reassignment the earlier reviewer stays requested too, and a review from either one completes it.

## What isn’t chased

-   Draft pull requests (unless you turn that off).
-   Pull requests with failing checks, if your policy waits for passing checks.
-   Repositories you haven’t turned on, and hosts you’ve disconnected.
-   Everything, while a workspace’s trial or subscription has lapsed. See [Billing](https://nudgepr.dev/docs/billing#lapsed).
