Merge governance for GitHub

Enforce release rules beyond CI.

Merge Preflight evaluates pull requests against your policies including:

external state: Jira/Linear issue status, Sentry ongoing incident;
time windows (example: block merges on Friday evenings);
branch naming, commit/PR body discipline.

Deterministic result, remediation actions advised, audit trail preserved.

Configure a repository Read the documentation

Merge Preflight senseisoft/payments-api · PR #1842

Blocked

Blocked by release policy

1 blocker · 11 rules passed

Jira issue is in an allowed state Pass

Release window is open Pass

Critical Sentry issue is active Block

SENTRY · PAYMENTS-2K1 PAYMENTS-2K1 is still active.

Resolve the issue or use an authorized bypass.

Commit 4f91a2c Decision recorded

What the check evaluates

CI reports on the code. Merge Preflight evaluates the conditions around the change each time the pull request is opened or updated.

Condition Conclusion Details

Jira or Linear issue is outside an allowed state Block Observed state and required state

Critical Sentry issue is active Block unrelated change Issue that triggered the policy

Release freeze is active Apply freeze policy Window, reason, and permitted exception

Bypass is submitted Accept or reject Authority, actor, and stated reason

How it fits into the workflow

Merge Preflight evaluation runs in response to pull request events and updates check verdict on GitHub. Policy can be defined for the organization and overridden by a repository.

Pull request: The author sees the conclusion, supporting evidence, and remediation.
Admin console: Release owners manage policy and review evaluations and bypasses.

$ 149 per protected repository
per month

Unlimited contributors, unlimited number of pull requests & checks.

Configure a repository

On-prem version available.

If you're nonprofit or open source, we might have free licenses for you.

Our support is human only.