How to configure PR review
PR review usage lives in Settings → Usage, and what BattleTest posts to your PRs is controlled from Settings → Integrations. For the limit figures themselves, see Limits & Quotas.
Monitor your review usage
Section titled “Monitor your review usage”Open the Usage tab
Go to Settings → Usage.
Read the meters
Each limit has a live meter showing current usage and when its window resets. Hourly windows reset on a rolling basis; monthly caps reset on the first of each UTC month. Reset times are shown in your local timezone.
Which branches get reviewed
Section titled “Which branches get reviewed”BattleTest reviews pull requests that target your repository’s default branch. This is zero-config and applies automatically. A PR opened against any other base branch (for example, an intermediary feature-A → feature-B merge) is skipped so it doesn’t burn your review limits.
To make the review a required merge gate on the default branch, add a GitHub branch protection rule. See How to require security review before merging.
What happens when you hit your limit
Section titled “What happens when you hit your limit”When your advanced review limit is reached, BattleTest never drops the PR event; it falls back to a basic scan so every PR still gets at least partial coverage. The PR comment notes that the basic scan ran.
If both the advanced limit and the basic fallback limit are exhausted in the same window, BattleTest posts a non-blocking GitHub check run with the reset time; no PR event is ever silently dropped, and running out of quota never blocks a merge.
Control what BattleTest posts to your PRs
Section titled “Control what BattleTest posts to your PRs”You can change how much BattleTest writes to each pull request from Settings → Integrations → PR review output:
- Full (default): inline comments on each finding plus a summary report.
- Minimal: a one-line verdict with a link to the full report, no inline diff comments.
- None: nothing is posted to the PR. The
BattleTest Security Reviewcheck run and the report dashboard still update.
Configure notifications
Section titled “Configure notifications”See How to configure notifications.
When you regularly hit a limit
Section titled “When you regularly hit a limit”Hitting the hourly or monthly advanced-review limit is not an error state. A basic scan runs instead, the pull request still gets coverage, and the PR comment says which mode ran. The limits and how each window resets are documented in Limits & Quotas.