GitHub troubleshooting

No review on a new pull request

• Confirm the repository is included in the MergeGuards GitHub App installation.
• Check that the PR is not in draft mode (if you rely on reviews only on ready PRs).
• Wait a minute and refresh—the first review can take a moment on large diffs.

Commands ignored

• Post @mergeguard-followup and @mergeguards deep-scan on the PR Conversation tab.
• Post @mergeguards fix as a reply on a MergeGuard inline comment on Files changed.
• Commands must be from a human user, not another bot.

Deep-scan blocked

Deep scan requires your GitHub App installation to be linked to a MergeGuard workspace on a paid plan. See Plans & limits.

Upgrade or limit message missing on the PR

When a review is blocked by your plan (monthly review cap or untracked repo), MergeGuard tries to post an explanation on the PR Conversation tab. If you see nothing, confirm the MergeGuards App still has access to the repository and that Issues and Pull requests are set to read/write on the app.

Review failed — retry with the checkbox

After a failed review run, look for a MergeGuard comment on the Conversation tab that includes:

- [ ] 🔍 Trigger review

Check the box to retry the full review. You must use a human GitHub account (not a bot). The checkbox only works on Conversation comments—inline comments on Files changed do not support this flow.

If checking the box does nothing, verify the GitHub App is subscribed to Issue comments (in addition to Pull requests) and that your API deployment includes the latest MergeGuard release.

You can still re-run manually anytime with @mergeguard-followup on its own line.

GitHub account not linked to your workspace

MergeGuard signs you in with Connect GitHub or Connect GitLab only—no separate password. Use the same GitHub user that installed the MergeGuards App, or link the installation from Dashboard → Repositories.