u/maruan21

I recently wrote a post on this subreddit about MergeMe and got some really positive feedback, so I wanted to post an update with some cool new features that I've added!

Some of the key features that I showed off last time were:

• One Slack message per MR that updates in place (open > in review > approved > merged)
• Review comments as thread replies on that card
• Per-project channel routing - each project can map to whichever Slack channel you want
• GitLab @ mentions ACTUALLY ping the right person on Slack with a one-time username map
• GitLab.com via OAuth - webhooks registered for you
• Self-hosted GitLab - paste a webhook URL into your instance
• You can set up label routing too, an MR with a "bug" label goes to #qa-reviews instead

--------

Some of the new features:

• You can now sign in via Google, GitHub & GitLab SSOs
• You can choose when the Slack card gets posted much more granularly now (e.g. custom comments / in review / in draft)
• CI status of the MR can now be shown directly on the Slack card (check out the last slide on this post to see an example)
• You can now self host MergeMe! A few of you here requested it & I also got some direct requests so I pushed it up the roadmap.
  • Use the "Get in touch" button on https://mergeme.dev/#pricing regarding self hosting

If your team already works tightly in Slack and you ping your colleagues "hey can you review this again" then mergeme.dev might just be a great inclusion to your workflow!

Let me know what you think!

Coming from GitHub and the 100s of integrations for it, the GitLab and especially the GitLab Self Hosted marketplace felt dire.

I was very used to my PRs (and now MRs) landing in a Slack channel like #fe-reviews, and the comments & reviews on it to land in that Slack thread. It meant I never missed comments and my PR/MRs were reviewed MUCH quicker.

No other tool that does what I'd like in this way supports GitLab, so I built mergeme.dev (...and included GitHub too so you guys don't feel left out)

Some of the key features that I wanted myself (and I'm sure others will appreciate) are:

• One Slack message per PR/MR that updates in place (open > in review > approved > merged)
• Review comments mirrored as thread replies on that card
• Per-project/repo channel routing - each project/repo can map to whichever Slack channel you want
• GitLab / GitHub @ mentions ACTUALLY ping the right person on Slack with a one-time username mapping
• GitHub.com via GitHub App installation
• GitLab.com via OAuth - webhooks registered for you
• Self-hosted GitLab - paste a webhook URL into your instance (check out the docs)
• You can set up label routing too, a PR/MR with "bug" as it's label goes to #qa-reviews instead
• [New] The CI status can be shown directly in the Slack card

If your team already works tightly in Slack and you ping your colleagues "hey can you review this again" then mergeme.dev might just be a great inclusion to your code review workflow!

I recently joined a new company and coming from GitHub and the 100s of integrations for it, the GitLab and especially the GitLab Self Hosted marketplace felt dire.

I was very used to my PRs (and now MRs) landing in a Slack channel like #fe-reviews, and the comments & reviews on it to land in that Slack thread. It meant I never missed comments and my PR/MRs were reviewed MUCH quicker.

Other than Axolo, no other tool that does what I'd like supports GitLab, so I built mergeme.dev (...and included GitHub too so you guys don't feel left out 😅)

Some of the key features that I wanted myself (and I'm sure others will appreciate) are:

• One Slack message per PR/MR that updates in place (open > in review > approved > merged)
• Review comments mirrored as thread replies on that card
• Per-project/repo channel routing - each project/repo can map to whichever Slack channel you want
• GitLab / GitHub @ mentions ACTUALLY ping the right person on Slack with a one-time username mapping
• GitHub.com via GitHub App installation
• GitLab.com via OAuth - webhooks registered for you
• Self-hosted GitLab - paste a webhook URL into your instance (check out the docs)
• [New] You can set up label mapping too, a PR/MR with "bug" as it's label goes to #qa-reviews instead

If your team already works tightly in Slack and you ping your colleagues "hey can you review this again" then mergeme.dev might just be a great inclusion to your workflow!

----

Aside from this, I am genuinely curious as to how people handle this problem in their own setup?

My personal story before MergeMe was that I set up webhooks into Slack from GitLab directly and I made a custom webhook triggered workflow to send myself messages when my own MRs were responded to. It was a MESS to look at and it's what unironically pushed me to build a better tool lmao.

(originally posted in r/gitlab but I also wanted to mention that it supports GitHub)

I recently joined a new company and coming from GitHub and the 100s of integrations for it, the GitLab and especially the GitLab Self Hosted marketplace felt dire.

I was very used to my PRs (and now MRs) landing in a Slack channel like #fe-reviews, and the comments & reviews on it to land in that Slack thread. It meant I never missed comments and my PR/MRs were reviewed MUCH quicker.

Other than Axolo, no other tool that does what I'd like supports GitLab, so I built mergeme.dev

Some of the key features that I wanted myself (and I'm sure others will appreciate) are:

• One Slack message per MR that updates in place (open > in review > approved > merged)
• Review comments as thread replies on that card
• Per-project channel routing - each project can map to whichever Slack channel you want
• GitLab @ mentions ACTUALLY ping the right person on Slack with a one-time username map
• GitLab.com via OAuth - webhooks registered for you
• Self-hosted GitLab - paste a webhook URL into your instance
• [New] You can set up label mapping too, an MR with "bug" as it's label goes to #qa-reviews instead

If your team already works tightly in Slack and you ping your colleagues "hey can you review this again" then mergeme.dev might just be a great inclusion to your workflow!

----

Aside from this, I am genuinely curious as to how people handle this problem in their own setup?

My personal story before MergeMe was that I set up webhooks into Slack from GitLab directly and I made a custom webhook triggered workflow to send myself messages when my own MRs were responded to. It was a MESS to look at and it's what unironically pushed me to build a better tool lmao.