Why did Qodex skip my PR?
Qodex may receive a GitHub PR event and intentionally skip review. Most skipped reviews are policy decisions, not platform failures. Common causes include draft PRs, non-reviewable GitHub actions,.qodex.yaml opt-out, an unlinked repo, lost GitHub App access, or webhook signature failure.
Check these first
| Reason | What it means | What to check |
|---|---|---|
| Non-reviewable action | The webhook action is not one Qodex reviews | Confirm the action is opened, synchronize, reopened, or @qodex review. |
| Draft PR | Qodex waits for the PR to be ready | Mark the PR ready for review and push again. |
.qodex.yaml opt-out | pr_review.enabled is false | Inspect .qodex.yaml on the PR branch. |
| Repo not linked | No Qodex project is mapped to the repo | Check Settings > Integrations > GitHub. |
| App access lost | The GitHub App no longer has repo access | Reinstall the app or re-add the repo. |
| Signature failed | Webhook secret mismatch | Check server logs and GITHUB_APP_WEBHOOK_SECRET. |
Where the reason appears
Open the PR’s Checks tab. Many intentional skips create a neutral Qodex Check Run with the reason in the title or summary. If there is no Check Run, check GitHub webhook deliveries and Qodex server logs. That usually means the event did not reach a linked project, or signature verification failed before Qodex could create a result.Why Qodex acknowledges skipped events
Qodex returns a successful webhook response for intentional skips so GitHub does not retry the same event. The skip means “Qodex received this, but policy says not to review it.”Next steps
How a review fires
Follow the full review lifecycle.
Troubleshooting PR review
Debug missing reviews.
.qodex.yaml reference
Check repo-level review settings.
Connect a repo
Confirm the repo is linked to a project.