Merger verdicts
Merge, reject, or escalate, weighing CI, findings, blast radius, and history. Risky changes go to a human.
Merger returns a verdict on every open pull request. Your rules decide what clears without a human, and Insights shows whether it works.
Merger makes the call, your rules bound it, and the dashboards tell you when to widen them.
Merge, reject, or escalate, weighing CI, findings, blast radius, and history. Risky changes go to a human.
Hard gates plus written guidance per repository. Merge automatically or just label.
Resolve addressed threads and approve PRs that meet your conditions.
Triggers, checks, comment limits, and skipped paths, per repository.
Evaluated PRs, ready-to-merge rate, and the share merged without a human.
Accepted and rejected suggestions per agent.
Bugs caught versus reported, and time to merge against a pre-Baz baseline.
Only where a rule allows it. Uncertain changes always escalate.
No. They compute from review activity.
Yes. Start manual, then widen the rules as the numbers earn it.
Connect a repository and see Merger's verdicts and your numbers on real PRs, or ask us how teams like yours set the rules.