Dash0 acquires Polar Signals

Last updated:

Set Up AutoMerge

Connect GitHub, approve the permissions AutoMerge needs, and start Dry run on your repositories.

Setup has two steps: connect GitHub so AutoMerge can read pull requests and CI results, then start Dry run on the repositories you want it to evaluate. Dry run makes no changes to your repositories. It comments its decision and approves or merges nothing.

Open Darkplane → AutoMerge in Dash0. Until Dry run has started on at least one repository, the page shows the Set up AutoMerge checklist instead of its tabs.

Prerequisites

  • Organization role: Connecting GitHub and starting Dry run require the Admin role in your Dash0 organization. Members see the checklist but cannot complete it.
  • GitHub access: A GitHub owner of each account you connect, to install the Dash0 GitHub App and approve its permissions.
  • CI checks (recommended): AutoMerge waits for CI checks to settle before it evaluates on its own, so its score includes the CI result. A repository without CI checks needs Wait for CI turned off, as described in Configure a Repository.

Step 1: Connect GitHub

AutoMerge uses the same GitHub integration as Agent0 and AI SDLC Insights. If it is already installed, the checklist marks this step as done.

  1. In the Connect GitHub step, click Connect GitHub.
  2. Follow Set Up GitHub Integration to install the Dash0 GitHub App and pick the repositories AutoMerge should evaluate.
  3. Return to Darkplane → AutoMerge. The step reads GitHub connected and shows how many repositories the app is installed on.

If the step reports a problem, click Open GitHub settings and fix the state it names:

  • The app has no repositories: Pick the repositories AutoMerge should evaluate.
  • This dataset can't read the integration: Add the dataset to the GitHub integration in Settings → Integrations.
  • The app is suspended: Unsuspend it in GitHub. While it is suspended, no pull request events arrive.

Approve the GitHub Permissions

AutoMerge needs three permissions from the Dash0 GitHub App:

  • checks: Post its advisory check run on each pull request.
  • pull_requests: Post its comment and its approving review.
  • contents: Merge pull requests in Auto-merge mode.

If an installation was set up before AutoMerge existed, a warning appears in the page header: AutoMerge needs one more GitHub permission, or a number of them. A GitHub owner of the account has to accept the updated Dash0 GitHub App. Click Review permissions on GitHub, approve the listed permissions, and the warning clears on its own within a minute.

Note

You can start Dry run before the permissions are approved, but its checks and comments only show on GitHub once they are.

Step 2: Start Dry Run

The Start Dry run button becomes available once a repository has sent its first event. If it is disabled, open or update a pull request in one of the connected repositories.

  1. Click Start Dry run. The Start AutoMerge in Dry run dialog opens.
  2. Under Repositories, select the repositories to evaluate. Every repository that is Off is selected by default. Repositories that are already running keep their mode and are not listed.
  3. Under When should it run?, choose a trigger:
    • On every pull request update (recommended): Runs after CI checks complete on each push, so the score includes the CI result.
    • Only when asked (Manual): Nothing runs until someone starts an evaluation on a pull request.
  4. Click Continue.
  5. In Basic rules, choose the criteria Dry run scores. All three default criteria are checked, weighted 34%, 33%, and 33%, and Dry run would approve when they score 75 or more. Unchecking a criterion drops it and spreads its weight over the others. Keep at least one checked.
  6. Click Start Dry run, then Done.

Dry run skips two kinds of repositories and lists them in the result:

  • Already running: A repository that is not Off keeps its current mode.
  • Path rules that approve or merge: A repository with an Auto-approve or Auto-merge path rule would act under Dry run too. Start it from its Configuration tab instead.

You can change every choice from the dialog later, per repository, in Configure a Repository.

Step 3: Verify the First Evaluation

  1. Open or update a pull request in a repository running Dry run.
  2. With the automatic trigger, wait for its CI checks to finish. With the manual trigger, use the Run evaluation link in the bot's comment on the pull request.
  3. On GitHub, check that the pull request shows a comment with the score card and a Darkplane auto-approval check.
  4. In Dash0, open the repository from the Repositories tab, then the Pull requests tab. The pull request shows a Decision and a Soft score.

If no decision appears, see Troubleshoot AutoMerge.

Further Reading