Bring code review
closer to where the work happens.

Mirror every pull and merge request into Slack as a single, updating card per PR/MR. No notification spam, no broken @mentions, no tab juggling.

Free forever for small teamsUp in 5 minutes
H
henryMergeMe12:16 AM
feat: add dark mode support
moorlint/frontend · feat/dark-mode main
● Open
H
@henryView PR
L
A
2 replies
0

webhooks processed

0

PR/MR cards postedPR/MR cards posted in Slack

0

live card updates

0

threaded comments

How it works

Open a PR. Watch it land in Slack.

Pick your code host, open a pull request, add review comments, then merge.

moorlint / frontendPull requests
Open a pull request
feat/dark-modemain
feat: add dark mode support
Adds system-aware dark mode via prefers-color-scheme with a manual toggle stored in localStorage.
MergeMe
A
Acme
Channels+
H
henry
# eng-frontend
E
emmaMergeMeYesterday 9:14 AM
fix: resolve login race condition
moorlint/frontend · fix/race-cond main
✓ Merged
E
@emma·1 / 1 approvedView PR
Message #eng-frontend

Inside MergeMe

One place to wire everything up.

Set it up once, then get back to shipping.

01

Connect every code host

GitHub.com, GitLab.com, or GitLab self-hosted - install once per workspace, alongside the Slack workspace MergeMe posts into.

MergeMe integrations overview showing GitHub, GitLab, Slack, channel routing, and user mappings

02

Route repos to channels

Map each repository or project to a Slack channel. You can even route labels to specific channels.

Channel routing rules mapping GitHub and GitLab repos to Slack channels with label overrides

03

@mentions that resolve

Link GitHub and GitLab usernames to Slack profiles once. Every @mention in a PR/MR comment becomes a real Slack ping instead of dead text.

User mapping list linking GitHub and GitLab usernames to Slack profiles

04

Control what gets posted

Exclude bot accounts, choose when the first card goes out, gate it behind a comment trigger, and toggle CI status on cards - so reviews start exactly when you want them to.

Notification preferences for excluded usernames, card titles, and post trigger phrase

05

The payoff

One Slack message tracks the whole lifecycle - opened, approved, merged - with live CI status updating in place as your team ships.

Slack PR card with status Open and CI starting

What you get

Tuned for how engineering teams actually use Slack.

One updating card per PR/MR

The same Slack message is edited in place across the entire lifecycle. Skimming a channel actually tells you what's waiting on you.

Draft
9:04 AM
Review
9:38 AM
Merged
11:12 AM

@mentions that actually ping

Map GitHub/GitLab usernames to Slack profiles once. Every mention in a PR/MR comment becomes a real Slack mention.

Per-repo channel routing

Route each repo to its own channel. frontend > #eng-frontend, infra > #eng-infra. Nothing posts unless you mapped it.

Comments as thread replies

Review comments don't pollute the channel - they land as replies under the PR/MR message. The card stays clean, conversation stays threaded.

No code-host API token

Everything MergeMe needs comes from the webhook payload itself. Nothing reads your private code.

Label routing

Route open PRs/MRs by label - per repo.
Top matching rule picks the channel.

bug>Slack#bugs
documentation>Slack#documentation
enhancement>Slack#features

Reviewers can only pick up what they see

The slowest step in most PR/MR lifecycles isn't writing the code or reviewing it - it's waiting for a reviewer to notice. MergeMe surfaces PRs/MRs in the Slack channel your team is already in, with the right people @-mentioned, so they don't have to remember to check.

3-14hours

Average PR/MR pickup time

Time a PR/MR sits before anyone reviews it, on teams that aren't tracking it. Elite teams clear it in under an hour.

Source: LinearB engineering benchmarks

Pricing

Free for small teams.

Pay only for developers you actually map to Slack. Stripe-managed billing, billed monthly.

Free

Hobby

For small teams trying MergeMe.

£0forever
  • 1 channel mapping
  • 5 user mappings
  • Single updating Slack card per PR/MR
  • CI status on Slack cards
  • Comments mirrored as thread replies
  • @mention resolution
  • Label routing
Start free

No credit card required

Team

Team

Unlimited routing. Pay per developer.

£5per dev seat / month
  • Everything in Hobby, plus…
  • Unlimited channel mappings
  • 1 user mapping per seat · sold in blocks of 5
  • Multiple code hosts · GitHub, GitLab & GitLab self-hosted
Get started

Billed monthly · cancel anytime

On-prem

Want to self-host MergeMe instead?

Run MergeMe on your own infrastructure - ideal for teams with data residency or SSO requirements. Get in touch at hello@mergeme.dev.

Get in touch

Quiet your engineering channels by Friday.

Sign in with Google, GitHub, or GitLab, map your first repo to a channel, and watch the noise drop. Most teams are up and routing in under five minutes.