Docs · Help
Troubleshooting
Almost every setup problem is one of these five. Each fix takes under a minute.
No check on the pull request
The repo is not in the GitHub App's watched list. Open the app's settings on GitHub, choose the installation, and add the repo under repository access. The check appears on the next PR event: a push, or closing and reopening the PR.
No rings beside the files
- Confirm the extension is installed and enabled for github.com, then reload the PR files page.
- Open the popup. It should say Signed in as you. If it shows a sign-in link, sign in at readpr.dev and reopen the popup.
- Confirm you are on the Files changed tab of a PR in a watched repo. The extension runs only on
github.com/*/pull/*.
Check stuck on amber
The check is waiting on reading it has not seen. In order:
- Scroll the actual files. Time counts only while a file's rendered diff is on screen in a focused tab. Parking the tab open does not move the ring.
- Check who is required. With
requireAllReviewerson, every assigned reviewer must finish, and the summary names who remains. - Check for a new push. Each commit re-evaluates. Files whose diffs changed start over.
- Check the exclusions. Excluded files need no time, so they are never the blocker. The blocker is listed in the check summary.
Popup says the token is no longer valid
The token was revoked, usually from dashboard settings. Press Reconnect in the popup. If the browser is signed in on readpr.dev, a fresh token is minted on the spot.
Popup cannot reach Read PR
- Check your connection, then press Retry.
- If your team self-hosts, open Advanced in the popup and confirm the API base URL points at your deployment. The default is
https://readpr.dev.
Check says paused, not enforced
That is billing, not reading: the trial ended or a payment lapsed, so checks on private repos moved to neutral and stopped enforcing. Merges are not blocked. An owner can pick a plan on the billing page to resume enforcement. Details in Billing.