If a review does not run
Check these first:- The Git provider is connected in Integrations
- The repository appears in Repositories
- The repository is enabled for Code Review
- The pull request or merge request targets a covered branch
- The organization has trial or paid review capacity available
- The organization has not reached its pooled review limit, or spillover is enabled on a paid plan
- For GitHub, the GitHub App installation includes the repository
- For GitLab, the service account still has access and its token has not expired
Repository is missing
If a repository does not appear in Hacktron:- Confirm that the Git provider installation includes the repository.
- If the repository was recently added, go to Repositories and sync again.
- For private repositories, confirm the installation or service account has access.
Branch is not covered
If only some pull requests or merge requests are reviewed:- Confirm the target branch is covered in the repository settings.
- If coverage is limited to specific branches, pull requests targeting other branches are skipped.
Developer is not covered
If a developer is not covered by a Code Review seat, Hacktron leaves a pull request comment explaining that no seat is assigned. Check Billing to confirm the organization has trial or paid review capacity available. If auto-assigned seats are enabled and a new developer did not get assigned a seat, you may need to increase the auto-assignment seat limit.Review limit is reached
Code Review uses a pooled organization review limit each billing period. If the limit is reached:- On a trial, new reviews stop until the period changes or an owner starts the paid plan
- On a paid plan with spillover off, new reviews stop until the next billing period or until an owner enables spillover
- On a paid plan with spillover on, reviews continue and overage reviews are billed as spillover
Still stuck?
Emailhello@hacktron.ai with your organization name and details of the issue.