PR Review Didn't Run

When the GitHub App is wired up correctly, every PR shows a Scrubby check run within a minute or two of opening. If you’re not seeing it, work through this checklist.

Step 1: is the app installed on this repo?

Go to the Settings › GitHub Apps page on your repo (or your org’s page if it’s an org install). Confirm Scrubby is listed and that this specific repo is in the install scope.

If it’s not, install or extend the install at github.com/apps/scrubbyai.

Step 2: is the repo indexed?

Even with the app installed, Scrubby won’t review PRs on an unindexed repo. The check posts a status note explaining this rather than failing silently.

• Index from your AI editor: ask it to run scrubby_index with the owner/repo path.
• Or index from the dashboard’s repositories page.

If indexing itself is failing, see Indexing Stuck or Failing.

Step 3: did the webhook fire?

Open the GitHub App’s installation logs (org Settings › GitHub Apps › Configure › Recent deliveries). Look for the pull_request event for your PR.

• No event listed — GitHub didn’t fire the webhook. Usually means the install scope doesn’t include the repo, or the PR action wasn’t opened/synchronize/reopened (e.g. edited doesn’t trigger).
• Event listed but with a non-2xx response — Scrubby received but rejected it. Click into the delivery to see the response code.

Response	Meaning
401	Webhook signature failed verification. Internal issue; contact support with the delivery ID.
400	Malformed payload. Almost always an internal issue.
200	Scrubby accepted the event. If no review appears, the analysis job may have errored out.

Step 4: check the dashboard

The repo’s detail page on the dashboard shows recent analysis jobs. If a job for your PR is listed as failed, the dashboard will show the error.

Step 5: still nothing

Push a new commit to the PR. That fires another synchronize event and re-runs the review. Sometimes a transient backend issue causes a single delivery to fail; the retry usually clears it.

If the retry also doesn’t produce a review, contact support via the feedback page with:

• The PR URL.
• The delivery ID from the GitHub webhook log.
• The repo’s index status (from the dashboard).

Edge cases

Forks

By default, the GitHub App only runs on PRs from branches in the same repo. Forks are supported but require the App to have access to the fork as well. Most public-repo workflows don’t need fork-from-stranger reviews; if yours does, contact support.

Draft PRs

Draft PRs do trigger reviews by default. If you’d like to suppress reviews on drafts, set audit_preferences.skip_drafts = true from the dashboard’s account settings.

Branch protection

If your branch protection rules require a Scrubby check that’s never appeared, the PR will be blocked from merging. Add Scrubby to your install scope and re-trigger the review (push a commit). The check will appear on the next event.