AutoMerge is generally available

AutoMerge is generally available

AutoMerge, Dash0's approval agent, is out of beta. It scores the risk of every pull request and approves the low-risk ones, so your reviewers spend their time on the changes that need them.

The AutoMerge overview of a repository in Auto-merge mode, with tiles for auto-approved pull requests, intervention rate, time to merge and agreement with humans, auto-approved pull requests over time, criterion scores against the passing threshold, and merged pull requests by type

AutoMerge is Dash0's approval agent. It scores the risk of every pull request and approves the low-risk ones, so your engineers spend their review time where it matters and your team ships faster without giving up control. It has been in beta since 6 November, and from today it is generally available.

AutoMerge checks each pull request against the rules you set for its repository: protected paths, criteria that AI evaluators score, and a threshold. A pull request that AutoMerge does not approve goes through your regular review.

Start in Dry run

Connect GitHub or GitLab and pick your repositories. In Dry run, AutoMerge comments its decision on every pull request and approves or merges nothing. The comment shows the combined score against your threshold, the score and weight of each criterion, and the evidence behind each score. Its comments already help your reviewers, before you let it approve or merge anything.

An AutoMerge comment on a GitHub pull request in Dry run. It would approve with a score of 88.8 out of 100 against a threshold of 75, lists five criteria with their weights and scores, and explains the Blast radius score of 96

Move up when it has earned it

Dash0 compares every decision with what your reviewers did next and shows the result as Agreement with humans. When the decisions match your reviewers, switch the repository to Auto-approve, where AutoMerge approves and a person merges, or to Auto-merge, where AutoMerge approves and merges. Path rules give a path its own level. Mark migrations, infrastructure or billing code as Protected, and a pull request that touches them always goes to a person.

Each decision is on the repository's Pull requests tab, with the verdict, the deciding criterion and the score of every criterion. If a decision was wrong, say so with "Was this decision right?".

The decision record of an approved pull request: a combined score of 88.2 against a threshold of 70, the deciding criterion, and the score of each of four criteria

Your own criteria

Every repository starts with three criteria: Blast radius, Evidence quality and Change footprint. Change them or add your own. Each criterion has its own AI evaluator that scores the pull request from 0 to 100 and explains the score. You write its prompt, pick the tools it may use to read the code, the pull request and the history of the repository, set its share of the combined score, and set a floor below which it rejects the pull request by itself. You also set the threshold for the repository. Improve configuration asks Agent0 to propose a change to the configuration, which you preview before you apply it.

The criteria of a repository's AutoMerge configuration, with one criterion open to show its name, its 40% share, its rejection floor of 60, its prompt and the tools it may use, and the Improve configuration button

Test a change before it runs

The Testing tab replays a configuration change on past pull requests. It shows which decisions change and how the new decisions compare with your reviewers, while the running configuration stays as it is.

A test result on the Testing tab that compares configuration v4 with v1 on 25 recent merges, with 8 changed decisions and the outcomes approved and agreed, approved but should not have, held and agreed, and held but could have merged

Pricing

Each pull request that AutoMerge scores costs 1 AI credit, regardless of the number of evaluations. Dry run is charged like the other modes, because AutoMerge still scores the pull request. A test costs 1 AI credit for each pull request it replays. To stop the charges for a repository, set its mode to Off.

Organizations that existed before today get 14 days of AutoMerge free, from the first pull request it scores. The Dash0 trial covers new organizations. When your organization reaches its monthly AI credit limit, AutoMerge stops scoring and says so on the pull request.

Supported

AutoMerge works with repositories connected through the GitHub integration or the GitLab integration. On GitLab it scores merge requests the same way it scores pull requests. On GitHub, an admin approves the permissions AutoMerge needs for the GitHub App. On GitLab, the service account's token needs the api scope, so that AutoMerge can comment, approve and merge.

Read the AutoMerge documentation, or follow Set Up AutoMerge to start your first Dry run.