Dash0 acquires Polar Signals

Last updated:

About AutoMerge

Score every pull request with AI evaluators, then approve or merge the ones that clear your rules, starting in a Dry run that changes nothing.

AutoMerge scores each pull request and approves the safe ones. You start it in Dry run, where it only posts its decision as a comment until you switch it on.

Coding agents have made writing a change cheap. Reviewing it has not become cheaper, so pull requests queue up waiting for a person, including the routine ones nobody needed to read line by line. AutoMerge takes that routine share off your reviewers. It judges each pull request against criteria you control, holds back anything that touches the paths you protect, and lets a person decide everything it is not confident about.

Beta

AutoMerge is in public beta. It supports repositories connected through the GitHub integration.

How AutoMerge Works

For every evaluated pull request, AutoMerge:

  1. Pins the commit: It evaluates the head commit at the moment the evaluation starts. A new push starts a new evaluation.
  2. Applies hard gates: A pull request that touches a Protected path, or changes 3,000 or more files, is held for a person without being scored.
  3. Scores each criterion: One AI evaluator per criterion reads the change with a set of read-only evaluator tools and returns a score from 0 to 100 with a rationale. The default criteria are Blast radius, Evidence quality, and Change footprint.
  4. Decides: It weights the scores into a combined score and approves when that score reaches the repository's threshold and no criterion falls below its own floor.
  5. Reports and acts: It posts its decision as a comment and an advisory check on the pull request. Depending on the repository's mode, it then approves the pull request, or approves and merges it.

Every decision, score, and rationale is also recorded in Dash0, where you can compare the bot's decisions with your reviewers' and test configuration changes against past pull requests.

Modes

Each repository runs in one of four modes. The mode is the repository's default autonomy level, and path rules can raise or lower it for specific paths, down to Protected.

ModeWhat AutoMerge does
OffTakes no action on this repository.
Dry runComments its decision without approving or merging.
Auto-approveApproves qualifying pull requests. Never merges.
Auto-mergeApproves and merges qualifying pull requests.

A person always decides what AutoMerge does not approve. AutoMerge's check is advisory: it does not block merges unless you make it a required check in GitHub.

Getting Started

  1. Follow Set Up AutoMerge to connect GitHub and start Dry run on your repositories.
  2. Read Key Concepts to understand modes, scoring, and path rules.
  3. Follow Roll Out AutoMerge to move from Dry run to Auto-approve once its decisions match your reviewers.

Further Reading