Software Alternatives, Accelerators & Startups
Register | Login
Table of contents
  1. Comments
  2. Is it good?

โœ“
MergeMe.dev

GitHub & GitLab PR/MR notifications in Slack - one updating card per request, threaded comments, @mention mapping. Free for small teams. Setup in 5 minutes.

MergeMe sends GitHub pull request and GitLab merge request notifications to Slack for code review. Each PR or MR gets one Slack card that updates in place when status changes (opened, in review, approved, merged, and more) instead of posting a new Slack message for every event like the official GitHub and GitLab Slack apps.

Review comments appear as thread replies on that same card. GitLab and GitHub @mentions in comments can be mapped to Slack @mentions. Route different repos or projects to different Slack channels, with optional label-based routing. One workspace can connect GitHub.com, GitLab.com, and self-hosted GitLab at the same time.

Supported sources: - GitLab.com (OAuth, automatic webhook setup) - GitLab self-hosted (webhook URL and signing token you add in GitLab) - GitHub.com (GitHub App install)

Optional CI status on each card shows GitHub checks or GitLab pipeline rollup (e.g. CI: Running (2/5)) when enabled in Routing preferences.

Website: https://mergeme.dev Docs: https://mergeme.dev/docs

A startup from the United Kingdom.

(0 reviews)
Pricing:
Visit website Alternatives Status Page
MergeMe.dev

MergeMe.dev Reviews and Details

This page is designed to help you find out whether MergeMe.dev is good and if it is the right choice for you.

#Developer Tools #Code Collaboration #Productivity #Software Development #Slack

Screenshots and images

  • MergeMe.dev
    Image date //
    2026-08-20
  • MergeMe.dev
    Image date //
    2026-08-20
  • MergeMe.dev
    Image date //
    2026-08-20
  • MergeMe.dev
    Image date //
    2026-08-20
  • MergeMe.dev
    Image date //
    2026-08-20

Features & Specs

  1. Single updating Slack card

    One Slack message per PR or MR; status changes update the same card instead of posting a new notification every time.

  2. Threaded review comments

    GitHub/GitLab review comments post as replies on that card so the conversation stays in one place.

  3. Channel routing

    Send different repos or projects to different Slack channels from one workspace.

  4. User mention mapping

    Map GitLab/GitHub usernames to Slack users so @mentions in comments notify the right people.

  5. Multi-git workspaces

    Connect GitHub.com, GitLab.com, and self-hosted GitLab in the same MergeMe workspace.

  6. Self-hosted GitLab

    Works with on-prem GitLab via webhook URL and signing token; no need to expose GitLab to extra SaaS beyond MergeMe.

  7. Label routing

    Optional rules to route or filter notifications based on merge request labels.

  8. CI status on cards

    Optional rollup of GitHub checks or GitLab pipelines on the Slack card (e.g. CI: Running (2/5)).

Badges

Promote MergeMe.dev. You can add any of these badges on your website.

SaaSHub badge
Show embed code

Questions & Answers

As answered by people managing MergeMe.dev.

  1. Who are some of the biggest customers of MergeMe.dev?

    • MergeMe is in early commercial use with paying teams; we do not publish customer names without permission.

  2. What makes MergeMe.dev unique?

    • One updating Slack card per PR/MR - status changes edit the same message instead of flooding the channel with a new notification for every GitLab or GitHub event
    • Thread replies for review comments on that card, not separate Slack messages
    • GitHub.com + GitLab.com + self-hosted GitLab in one workspace, with per-project channel routing and optional label routing
    • @mention mapping so GitLab/GitHub mentions in comments resolve to Slack mentions
    • Optional CI rollup on the card (GitHub checks / GitLab pipelines) when enabled in preferences

  3. Why should a person choose MergeMe.dev over its competitors?

    • Less channel noise than the official GitHub and GitLab Slack apps, which typically post a new message per event
    • Clearer review threads - comments stay on one card as thread replies
    • More control - route repos/projects to different channels; map users for mentions; optional label rules
    • Multi-git - mixed GitHub + GitLab (including self-hosted) without juggling multiple tools
    • Straight setup - GitLab.com and GitHub via OAuth/App; self-hosted GitLab via webhook URL and signing token
    • Free Hobby tier for small teams; paid Team plan scales per developer seat

  4. How would you describe the primary audience of MergeMe.dev?

    Engineering teams and engineering managers who use Slack for day-to-day communication and GitHub or GitLab for code review, especially when:

    • the official Slack integration has made their dev channels unusable
    • they run GitLab self-hosted and need reliable MR notifications without another heavy platform
    • they have mixed GitHub + GitLab repos and want one notification setup
    • they care about routing (per-repo channels) and working @mentions in Slack

  5. What's the story behind MergeMe.dev?

    MergeMe started from a practical problem: teams loved Slack for collaboration but hated how official GitHub and GitLab Slack integrations treated every MR/PR event as a separate message. Channels became noisy, threads broke apart, and it was hard to see what actually needed review.

    The idea was simple - treat each pull request or merge request as one living Slack card that updates as review state changes, with comments as thread replies. From there it grew into routing, mention mapping, multi-git workspaces, and self-hosted GitLab support for teams that cannot or do not want to rely on the default apps.

Videos

We don't have any videos for MergeMe.dev yet.

Add video

Is MergeMe.dev good?

External links

We have collected here some useful links to help you find out if MergeMe.dev is good.

  • Public traffic stats of MergeMe.dev

    Check the traffic stats of MergeMe.dev on SimilarWeb. The key metrics to look for are: monthly visits, average visit duration, pages per visit, and traffic by country. Moreoever, check the traffic sources. For example "Direct" traffic is a good sign.

  • Domain Rating (DR)

    Check the "Domain Rating" of MergeMe.dev on Ahrefs. The domain rating is a measure of the strength of a website's backlink profile on a scale from 0 to 100. It shows the strength of MergeMe.dev's backlink profile compared to the other websites. In most cases a domain rating of 60+ is considered good and 70+ is considered very good.

  • Domain Authority (DA)

    Check the "Domain Authority" of MergeMe.dev on MOZ. A website's domain authority (DA) is a search engine ranking score that predicts how well a website will rank on search engine result pages (SERPs). It is based on a 100-point logarithmic scale, with higher scores corresponding to a greater likelihood of ranking. This is another useful metric to check if a website is good.

  • Public opinion on Reddit

    The latest comments about MergeMe.dev on Reddit. This can help you find out how popualr the product is and what people think about it.

Do you know an article comparing MergeMe.dev to other products?
Suggest a link to a post with product alternatives.

Suggest an article

MergeMe.dev discussion

Log in or Post with
Visit official website
mergeme.dev

Is MergeMe.dev good? This is an informative page that will help you find out. Moreover, you can review and discuss MergeMe.dev here. The primary details have been verified within the last quarter. So they could be considered up to date. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.

Loading...