Dash0 acquires Polar Signals

Last updated:

Troubleshoot AutoMerge

Fix AutoMerge evaluations that do not start, do not reach a decision, or do not act on GitHub.

Most problems come down to one of three causes: the evaluation never started, it started but did not reach a decision, or it decided but could not act on GitHub. Open the pull request's details on the repository's Pull requests tab first. Its Reason usually names the cause.

No Evaluation Starts

  • The trigger is Manual: With Manual, nothing is evaluated until someone starts an evaluation, through the Run evaluation link in the bot's comment or Evaluate now in Dash0. Switch Trigger to Automatic in the repository's Configuration tab to evaluate every push.
  • The repository has no CI checks: With Automatic and Wait for CI on, AutoMerge waits for CI checks that never report. Turn Wait for CI off.
  • CI is failing: In Auto-approve and Auto-merge, AutoMerge skips a push whose checks fail. Dry run still evaluates it.
  • The pull request is a draft or closed: AutoMerge evaluates only open, non-draft pull requests.
  • The pull request existed before the trigger changed: Switching to Automatic does not evaluate existing pull requests until they receive a new push.
  • The repository is Off, Disconnected, or Disabled: Check the mode and connection on the Repositories tab. A disconnected repository is no longer covered by any GitHub integration. Select it in the GitHub integration again.

No Decision Appears

If the Overview shows No decision from the bot yet, evaluations either did not run, or failed or were cancelled. The pull request's details show which:

  • Evaluation failed: If any criterion's evaluator fails, the whole evaluation fails and nothing is approved.
  • Evaluation cancelled: The evaluation was stopped before it finished.

In both cases, push a new commit to evaluate again. On a repository with the Manual trigger, you can also start one with Evaluate now in the pull request's details.

Nothing Shows on GitHub

  • Missing GitHub permissions: If the page header shows AutoMerge needs one more GitHub permission, a GitHub owner has to accept the updated Dash0 GitHub App. Until then, checks and comments do not appear. See Approve the GitHub Permissions.
  • Comments are suppressed: With Suppress comments on, for the repository or a matching path rule, AutoMerge posts no comment. The check run and any approval or merge still appear.

It Decided to Approve but Did Not

The pull request's Reason explains why:

  • It ran as a dry run: Either the repository is in Dry run, or a path rule held this pull request to a dry run. Check Ran as in the pull request's details.
  • A protected path: A file the pull request touches resolved to Protected, so the bot could not act on it whatever it scored.
  • The head moved: A new commit arrived while AutoMerge was acting. It evaluates the new commit instead.
  • CI was not green: AutoMerge does not approve a commit whose CI has not passed. It applies a withheld approval once CI settles, without scoring again.

Further Reading