Guides How-to

Keep GitLab merge requests moving in the Slack channels that own them.

Send GitLab merge request activity into focused Slack threads, with mapped reviewer mentions and pipeline changes beside the request.

Start free Read docs GitLab + Slack

How it works

Four steps from connection to a useful conversation.

1
Connect GitLab as a source and Slack as a destination in Connections.
2
Create a route from the GitLab project to the Slack channel where merge requests are reviewed.
3
Enable One thread per request so approvals, change requests, and pipeline updates remain in context.
4
Map GitLab accounts to Slack users under People to make reviewer mentions actionable.

FAQ

Yes. GitLab routes and messages use merge request and pipeline terminology, including GitLab references such as !77.

Yes. Add a route for each project-to-channel pairing, then choose the events each audience needs.

Yes. With pipeline status enabled, ForgeRelay posts the failure and recovery alongside the merge request.

Keep learning

Watch GitLab projects, open one Discord thread per MR, and keep pipeline failure and recovery beside the request.

Set a review reminder that reaches mapped reviewers in Slack or Discord after a request waits too long, then stays quiet.

Keep going

Free for up to three mapped people. Unlimited repos and notifications.

Start free