Troubleshooting

What to check when a review did not appear, came late, or said it could not run.

My pull request was not reviewed

Check the pull request's conversation for a comment from superdiffs — it says why when it skips (draft, plan limit, too many files, paused).
Make sure the repository is one superdiffs can access: GitHub → Settings → Applications → superdiffs → Repository access.
Pull requests opened before you installed are not all reviewed automatically. Comment @superdiffs review on one to review it now.
Drafts are skipped until they are marked ready for review, unless review.drafts: true is set.
Check /status for an outage.

The review is late

A review starts 30 to 60 seconds after the last push, so a burst of commits costs one review, not ten. Most reviews then finish in one to three minutes; very large pull requests take longer.

It said "Review couldn't run" or "Review timed out"

Something failed on our side for that commit. Comment @superdiffs review or push a new commit to try again. If it keeps happening, email hello@superdiffs.com with the pull request link.

It said this month's reviews are used up

Your plan's monthly allowance is spent. Reviews resume on the date in the comment, or immediately after upgrading in the dashboard.

Pull requests from forks are reviewed like any other. superdiffs reads code with a read-only token for your repository and never runs the contributor's code with your secrets. Commands are accepted only from people with write access.

Commands do nothing

Commands are honoured only from users with write access to the repository, and only in pull request comments — not in the pull request description. @superdiffs help lists them.

Stop reviews

@superdiffs pause stops reviews on one pull request; @superdiffs resume restarts them.
Pause the whole organization from the dashboard (Settings).
Uninstalling the GitHub App stops everything and deletes your review data.

Still stuck?

Email hello@superdiffs.com or see the contact page.