CI and findings state
Required checks passing or failing, and whether Baz findings on the PR are still unresolved.
Product
Merger
Trust a merge decision you can measure.
Merger evaluates every open pull request for merge readiness and returns a verdict: merge, reject, or escalate. Merger Agent Stats shows the evaluated volume, the ready-to-merge rate, and how much of it happened without a human in the loop.
Evaluated PRs412
Marked as Ready to Merge Share of evaluated PRs Merger judged safe to merge76% 313 / 412
Merged Without Human Input Share of evaluated PRs Merger merged on its own54% 223 / 412
Ready to Merge PR Breakdown
Merged Escalated Open
PR Throughput
Opened Merged
More agent metrics coming soon
What's inside
What Merger checks before it decides
Merger weighs CI state, unresolved findings, and repo-specific context, then returns merge, reject, or escalate. Escalation is the safety valve: uncertain or high-impact changes always go to a human.
Diff and repo context
The actual change, how broad or risky it is within the repository, and prior related commits.
Org guidelines and auto-approve rules
Team-specific review conventions and any auto-approve conditions already configured for the repo.
Escalation
Failed or pending CI, open critical issues, or high business impact routes the PR to a human instead of a verdict.
Merger Agent Stats
Evaluated PRs, ready-to-merge rate, merged-without-human-input rate, merge outcome breakdown, and PR throughput over time.
The shift
From queue triage to a measured verdict
Manual merge triageMerger
Every PR waits for someone to re-check CI and commentsMerger checks CI, findings, and context automatically
Stale PRs pile up waiting for a human passSafe PRs merge without waiting on a human
"Is this thing working?" is a guessMerger Agent Stats tracks the verdicts and outcomes
Read more
Get started
Let Merger clear the queue you can measure
Connect a repository and see Merger's verdicts on your real PRs, or ask us to walk through the stats on your own queue.