Dash0 acquires Polar Signals

Last updated:

Configure a Repository

Set a repository's AutoMerge mode, trigger, threshold, criteria, path rules, and advanced options.

Each repository has its own AutoMerge configuration. Open Darkplane → AutoMerge, select the repository on the Repositories tab, and open its Configuration tab.

Editing requires the Admin role. Other members can view the configuration but not change it. Changes take effect when you click Save. Discard drops unsaved edits.

Tip

Before you change criteria or the threshold on a busy repository, test the new configuration against past pull requests on the Testing tab. See Test a Configuration Change.

What It Does

The What it does card holds the settings that decide when AutoMerge runs and what it does with a decision. When Mode is Off, the other settings are hidden.

SettingOptionsDefaultWhat it controls
ModeOff, Dry run, Auto-approve, Auto-mergeOffWhat AutoMerge does with a decision. See Modes.
TriggerAutomatic, ManualManualWhen an evaluation starts. See Triggers.
Wait for CIOn, offOnShown for Automatic only. Waits for CI checks to settle before evaluating, which skips wasted evaluations on commits that are still building.
Acts at confidence0 to 10075The threshold. Anything scoring below it is held for a person.
Suppress commentsOn, offOffEvaluates and records the decision in Dash0, but posts no comment, so a reviewer's judgement is not anchored by the bot's. The check run and any approval or merge are unaffected.

The defaults apply to a repository that was never configured. The Start Dry run dialog in Set Up AutoMerge sets the mode to Dry run and the trigger you chose there.

Note

With Automatic and Wait for CI on, a repository without CI checks never starts an evaluation. Turn Wait for CI off for such repositories.

Criteria

The Criteria card lists the criteria the evaluators score. Click Add criterion to add one, or Remove criterion to drop one. Each criterion has:

  • Name: Shown in the bot's comment and in Dash0.
  • Share: Its weight, from 0 to 100 in steps of 5, as a percentage of the combined score. The shares of all criteria must total 100% before you can save.
  • Rejects below (optional): A floor. A score below it rejects the pull request on its own, whatever the combined score. See Criterion Floors.
  • Prompt: The guidance handed to the evaluator for this criterion.
  • Tools: The evaluator tools this criterion may use.

Saved criteria belong to the repository. When Dash0 improves its default criteria, repositories that already saved their own keep them.

Path Rules

The Path rules card overrides the mode for specific paths. A repository can have up to 50 rules, with up to 50 patterns each. With no rules, every file runs at the repository mode.

  1. Click Add rule. A new rule starts at level Protected.
  2. Give it an optional Name, such as Protected migrations. The name is only a label.
  3. Under Paths, enter one or more patterns, for example db/migrations/**. Click Add pattern for more.
  4. Choose the level the rule Applies: Protected, Dry run, Auto-approve, or Auto-merge.
  5. Optionally, name the authors the rule applies to. Without authors, it applies to everyone. With authors, choose what applies to everyone else: Repository default, Dry run, or Protected.
  6. Optionally, turn on Suppress comments to evaluate pull requests touching these paths silently.
  7. Click Save.

How rules combine is described in Path Rules.

Pattern Syntax

Patterns are case-sensitive and match the whole repository path.

PatternMatches
*Any characters within one path segment
**Any characters across path segments
**/Zero or more directories
?One character within a path segment
[abc]One listed character
[a-z]One character in a range
[!abc], [^abc]One character not listed
[[]A literal opening bracket

Character classes never match /. Unclosed or invalid classes, such as [z-a], are literal. Characters not listed above are literal, and backslashes do not add escaping.

Advanced

The Advanced card holds options most repositories leave at their defaults:

  • Fast-track verified reverts: Off by default. Approves a pull request that exactly reverts one AutoMerge approved, without a full evaluation. Anyone can open the revert, and the reverted pull request can be of any age. In Auto-merge mode, the revert is merged too.
  • System prompt addition: Up to 4,000 characters, handed verbatim to every evaluator on this repository. Evaluators treat it as fact, so keep it accurate and current. Use it for context the code does not show, such as which directories carry the highest consequences.
  • Approval comment: Up to 1,000 characters, appended to the bot's comment when it approves a pull request. Use it for policy or audit notes.
  • Learning phase: Click Start backfill to reconstruct authorship history from the default branch. The Path authorship evaluator tool reads this history. It runs in the background and can take a while on a large repository. Run again replaces the existing data.

Version History

Every save creates a new version. The Version history card lists each version with its status, Live or Superseded, what changed, who saved it, and when. To go back to an earlier configuration, click Restore as draft on its row, review it, and click Save.

Further Reading