ForgeRelay

Guides How-to

Relay GitLab merge requests into Discord threads your team actually reads.

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

Start free Read docs GitLab + Discord

How it works

Four steps from connection to a useful conversation.

  1. 1

    Connect GitLab via OAuth, watch the projects you care about, and install the Discord bot into your server.

  2. 2

    Create a route from a GitLab project to a Discord channel and select merge request events.

  3. 3

    Map GitLab users to Discord members under People for accurate mentions.

  4. 4

    Turn on MR pipeline status so failures and recoveries update the same thread.

FAQ

Questions people ask before connecting.

Yes. With a GitLab source, the UI and messages say merge request and pipeline, and reference !77 rather than #77.

Yes. Set MR pipeline status to post as a new message when a failing pipeline needs channel-level visibility.

No. The bot needs Send Messages, Create Public Threads, Send Messages in Threads, and Read Message History in the channels it posts to.

Keep learning

Related guides for this workflow.

GitLab merge request notifications in Slack

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

Read guide

Send CI failures and recoveries to Slack or Discord

Keep failing checks, jobs, and recoveries attached to the pull or merge request conversation instead of scattering alerts across chat.

Read guide

Keep going

Related product pages.

Product model

Routes, threads, people and pipelines.

Pricing

Free for 3 mapped people; Team by seats.

All guides

More how-tos for Slack and Discord relays.

Ready to relay the next review?

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

Start free