Routing

Preferences

Workspace-wide settings that apply to every mapped repository and connected git provider. Open Routing > Preferences in the dashboard.

Excluded usernames

Blocklist git usernames whose PRs/MRs and comments should not be sent to Slack. Useful for bots and automation accounts. Matching is case-insensitive. You can exclude up to 50 usernames per workspace.

When to post the Slack card

Workspace-wide control over the first Slack card for each PR/MR:

• Post when opened - including drafts/WIP
• Post when ready for review - default; waits for draft/WIP to be marked ready
• Post when a phrase is commented - waits until a PR/MR comment exactly matches your configured phrase (case-insensitive, trimmed).

This interacts with label routing: label rules are evaluated when the card is first posted (on open, ready_for_review, or when the phrase comment arrives).

Show PR / MR number in card title

On by default. Include the PR/MR number in the Slack card heading (for example !3723 Edit README on GitLab or #42 Edit README on GitHub). Turn off for title-only headings.

Show CI status on Slack cards

Off by default. When enabled, MergeMe adds a CI line to each posted PR/MR card (for example CI: Running (2/5)). If optional (non-blocking) checks exist, a second bucket appears, such as Optional CI: Passed (1/1). The line updates in place as GitHub checks or GitLab pipelines run and finish. It is display-only - CI does not change review status, card color, or thread behavior, and it does not post extra Slack messages.

If CI data is missing (no pipeline yet, stale commit, or missing GitHub permissions), the row is hidden rather than showing an error.

• GitHub.com - MergeMe needs Checks: Read and Commit statuses: Read on the GitHub App. GitHub may prompt you to approve these after an app update. If you skip the prompt, cards keep working without the CI line. See GitHub setup.
• GitLab.com - New channel mappings register pipeline events automatically. Enable this preference, then open or update an MR so a pipeline webhook can populate the line.
• GitLab self-hosted - Enable Pipeline events on the group or project webhook in addition to merge request and comment events. See self-hosted setup.