GitLab Slack integration
GitLab merge request notifications in Slack
MergeMe is a GitLab Slack integration for code review: one updating Slack card per merge request, threaded comments, @mention mapping, and channel routing. Works with GitLab.com and self-hosted GitLab.
What is this?
MergeMe connects GitLab merge requests to Slack. When an MR is opened, reviewed, approved, or merged, your team sees a single Slack card in the right channel. The card updates in place instead of flooding the channel with a new message for every webhook event.
The official GitLab Slack app posts a new Slack message for every event. MergeMe keeps one message per merge request and edits it as status changes. Review comments land in the thread on that card.
Official GitLab Slack app vs MergeMe
| Feature | Official GitLab Slack app | MergeMe |
|---|---|---|
| Slack messages per MR | New message for many events | One card, updated in place |
| Review comments | Often separate messages | Thread replies on the MR card |
| @mentions in comments | Plain text usernames | Mapped to real Slack @mentions |
| Channel routing | Limited | Per-project channel mappings and label routing |
| Self-hosted GitLab | Varies by setup | Webhook URL + signing token from MergeMe |
| Multi-git per workspace | GitLab only | GitHub.com + GitLab.com + self-hosted together |
See a focused comparison on GitLab Slack app alternative.
Features
- Single updating Slack card per merge request - status changes update the existing message
- Thread replies for GitLab review comments on the same card
- User mapping: GitLab @mentions become Slack @mentions
- Channel routing: send different GitLab projects to different Slack channels
- Label routing: override the default channel when specific labels are present
- GitLab.com via OAuth (~5 minutes) or self-hosted GitLab via webhook (~10 minutes)
- Webhook payloads only - MergeMe does not read private code
FAQ
- How is MergeMe different from the official GitLab Slack app?
- The official GitLab Slack app posts a new message for every merge request event. MergeMe keeps one Slack card per merge request and updates it in place as the MR moves through review.
- Does MergeMe work with self-hosted GitLab?
- Yes. Connect self-hosted GitLab with a webhook URL and signing token from MergeMe. You can run GitLab.com, self-hosted GitLab, and GitHub.com in one workspace.
- How many Slack messages does MergeMe send per merge request?
- One. The same Slack message is edited as the MR is opened, reviewed, approved, or merged. Comments post as thread replies on that card.
- Does MergeMe read my source code?
- No. MergeMe processes webhook payloads from GitLab only. It does not clone repositories or read private code.
- How much does MergeMe cost?
- Hobby is free (1 channel mapping, 5 user mappings). Team is from £5 per developer seat per month with a 10-seat minimum.
- How long does GitLab setup take?
- About 5 minutes on GitLab.com via OAuth. Self-hosted GitLab takes about 10 minutes to paste webhooks and map projects.
Start free on MergeMe
Hobby plan is free for small teams. Setup takes about 5 minutes.