MergeMe mirrors pull requests and merge requests from GitHub and GitLab into Slack. Each PR or MR gets a single Slack message that updates in place as it moves through the review lifecycle - opened, in review, approved, changes requested, merged, or closed.
Review comments appear as thread replies under that card, so channels stay readable instead of filling up with one notification per event.
Many teams start with the official GitHub or GitLab Slack apps and hit the same problems: every webhook event becomes a new message, @mentions in code comments do not ping the right people in Slack, and there is no easy way to route different repos to different channels. MergeMe is built specifically for that code-review notification workflow.
Supported code hosts:
- GitHub.com - install the MergeMe GitHub App; webhooks are registered automatically
- GitLab.com - connect via OAuth; MergeMe registers project webhooks for you
- GitLab self-hosted - paste a webhook URL and signing token into your instance (no inbound access from MergeMe required)
One MergeMe workspace can connect multiple git sources at once (for example GitHub and GitLab together). You map repos and projects to Slack channels, optionally map GitHub/GitLab usernames to Slack users for real @mentions, and can use label-based routing to send PR/MRs with specific labels to different channels.
MergeMe processes webhook payloads only. It does not read your private source code. Setup typically takes about five minutes: sign in at mergeme.dev, connect Slack, connect your git provider, add channel mappings.
Pricing: Free Hobby plan (1 channel mapping, 5 user mappings, no credit card). Team plan from £5 per developer seat per month with unlimited channel mappings and multiple code hosts.
