Pre-merge Checks

Define rules that run automatically after every PR review. Set up gates to block merges when code quality standards aren't met.

How it works

Create a check

Choose a rule type and set your threshold — for example, block if any security issue is found.

Open a PR

When a PR is opened or updated, CodePeel runs your review as usual.

Checks run automatically

After the review completes, your checks evaluate the findings.

GitHub status posted

A commit status appears on the PR — green checkmark if all pass, red X if an error-severity check fails.

Pre-merge Checks page showing active checks with pass/fail stats

Severity levels

Errorblocks merge

Checks with error severity will block the merge. GitHub shows a red X. The PR cannot be merged until the check passes.

Warningsoft warning

Checks with warning severity show a yellow indicator but do not block the merge. Use this for non-critical quality gates.

Passall good

When a check passes, GitHub shows a green checkmark. No merge blocking.

Check types

Block if any security issue is foundsecurity blocker

Use this for zero-tolerance security policies. If even one security issue is detected, the check fails and the merge is blocked.

Block if too many issues are foundmax issues

Set a number threshold. If the total count of all issues (bugs + security + performance) exceeds your threshold, the check fails.

Block if too many bugs are foundbug density

Set a threshold for bug count specifically. If more bugs than your threshold are found, the check fails.

Block if any critical issue is foundcritical findings

Critical issues are the most serious findings. If any critical-severity issue is detected, the merge is blocked.

Custom rule with your own thresholdcustom

Same as Max Issues — set a custom threshold for total issues allowed.

Stats on each check

Each check shows pass and fail counts. These update after each PR review. The bar shows the ratio — green for passes, red for fails.

"Last triggered" shows when the check last ran. If a check has never run, the field is empty — that means no PR review has been completed yet.

Recent History

The Recent History section shows the last 20 check runs (both passes and fails) across all your repositories. Each row shows the result, which check triggered, which repository, and when it ran.

Getting started

1. Go to Pre-merge Checks

2. Click "Add Check"

3. Choose a check type, set a name and threshold

4. Set severity (error blocks merge, warning is a soft warning)

5. Save — your check is now active

Go to Pre-merge Checks

← All docsCodePeel