CI and findings state
Whether required checks pass, and whether Baz findings on the PR are still unresolved.
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 volume, the ready-to-merge rate, and how much happened without a human.
What Merger checks before it decides
Merger weighs CI, unresolved findings, and repo 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 change itself, how risky it is within the repository, and prior related commits.
Org guidelines and auto-approve rules
Your review conventions and any auto-approve conditions set for the repo.
Escalation
Failed or pending CI, open critical issues, or high business impact routes the PR to a human.
Merger Agent Stats
Evaluated PRs, ready-to-merge rate, merged-without-human rate, outcome breakdown, and throughput over time.
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
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.