Try it for yourself.
Check out how a comment from GitHub shows up under the same
Slack card in this interactive demo.
moorlint / frontend
Open a pull request
feat/dark-modeintomain
Title
# eng-frontend
Pull requests and merge requests
Waiting for the request to open.
Connect all the hosts.
GitHub.com, GitLab.com, or GitLab self-hosted. Installed once per workspace.
Route each repo.
Nothing reaches Slack unless you mapped it. A label can send it somewhere else.
Mentions that ping.
A GitHub or GitLab username becomes a real Slack mention.
Tailor the preferences to how you work.
Drafts can wait. CI can stay off the card until you turn it on.
You forgot to review it, didn't you?
A Slack digest of open PRs and MRs, on the days you pick.
3-14 hours
That is how long a pull request or merge request usually waits for a first review. MergeMe helps your team bring that number down.
Source: LinearBFree until the routing gets bigger.
Hobby is free. Team is £5 per developer you map to Slack.
| Feature | Hobby£0Start free | Team£5Get started |
|---|---|---|
| Channel mappings | 1 | Unlimited |
| User mappings | 5 | 1 per seat, sold in blocks of 5 |
| Stale PR/MR reminders | 1 repo or project | Unlimited |
| Updating Slack card | Yes | Yes |
| CI status on cards | Yes | Yes |
| Comments as thread replies | Yes | Yes |
| @mention resolution | Yes | Yes |
| Label routing | Yes | Yes |
| Multi-git workspace | One channel | GitHub, GitLab, and GitLab self-hosted |
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.