MergeMe

MergeMe is a Slack integration built for engineering teams that want pull request and merge request activity surfaced directly in their Slack channels — without notification spam or tab juggling. Made by Moorlint Corporation and built in London, it connects GitHub.com, GitLab.com, and self-hosted GitLab to a Slack workspace, posting one updating card per PR/MR that evolves in place across the full lifecycle.

What It Is

MergeMe sits between your code host and Slack, listening for webhook events and translating them into a single, editable Slack message per PR/MR. Instead of a flood of separate notifications for each status change, one card tracks the PR from draft through open, approved, and merged — updating in place. Review comments land as thread replies under that card rather than polluting the channel. The tool is webhook-driven and, according to the product page, requires no code-host API token because everything it needs comes from the webhook payload itself.

How the Routing Works

Setup follows a five-step model: connect a code host, connect a Slack workspace, map repositories or projects to channels, link GitHub/GitLab usernames to Slack profiles, and configure notification preferences. Key routing capabilities include:

• Per-repo channel routing — each repository or GitLab project maps to a specific Slack channel (e.g., frontend repo → #eng-frontend)
• Label routing — open PRs/MRs can be routed to different channels based on labels, with the top matching rule winning
• User mappings — GitHub/GitLab usernames are linked to Slack profiles once, so every @mention in a PR comment becomes a real Slack ping
• Post trigger control — teams can gate when the first card goes out, exclude bot accounts, and toggle CI status display on cards

Reminders Feature

A newer addition (marked "New" on the product page) lets teams schedule Slack digests of open PRs/MRs that have been sitting too long. Reminders are configurable per repo/project with staleness thresholds, digest schedules (e.g., weekdays at 09:15 Europe/London), and an option to ignore very old PRs. This targets the PR pickup-time problem — the product page cites LinearB engineering benchmarks noting that average PR pickup time on teams not actively tracking it can run 3–14 hours.

Supported Integrations and Setup Paths

MergeMe supports three code host connection methods:

• GitHub.com — via a GitHub App install on an org; no per-repo webhook setup needed
• GitLab.com — via OAuth with automatic webhook registration
• GitLab Self-Hosted — via manual webhooks or a GitLab Application with OAuth, project pickers, and automatic webhooks

A self-hosted deployment option is also available for teams with data residency or SSO requirements, available by contacting the team directly.

Deployment Model and Privacy Stance

The cloud-hosted version processes webhooks without storing private code content — the product page states MergeMe reads only what arrives in the webhook payload and holds no code-host API token. The privacy policy and terms of service are documented at mergeme.dev/docs. A self-hosted path exists for teams that need to run MergeMe on their own infrastructure.

Current Status

MergeMe is actively shipping. The homepage references a public roadmap and changelog at roadmap.mergeme.dev, and the Reminders feature is labeled "New," indicating recent product movement. The product page reports processing over 30,000 webhooks and posting over 1,000 PR/MR cards in Slack, with over 2,600 live card updates and 1,200 threaded comments — figures presented by the vendor on the homepage.