ForgeRelay

Guides How-to

Bring GitHub pull requests into Discord — one conversation at a time.

Route GitHub pull requests to a Discord channel, open one public thread per request, and keep reviews and checks together.

Start free Read docs GitHub + Discord

How it works

Four steps from connection to a useful conversation.

  1. 1

    Connect GitHub as a source and install ForgeRelay in the Discord server where your team reviews work.

  2. 2

    Create a route from the GitHub repository to the Discord channel that owns its review conversation.

  3. 3

    Turn on One thread per request so later approvals, comments, and checks stay below the original pull request.

  4. 4

    Map GitHub users to Discord members under People so review requests reach the right teammate.

FAQ

Questions people ask before connecting.

When One thread per request is enabled, the first matching event starts a public Discord thread and later updates stay there.

Yes. Each route controls one repository-to-channel pairing, so ownership and noise stay separate.

Yes, when their GitHub account is mapped to a Discord member under People. Unmapped accounts remain plain text.

Keep learning

Related guides for this workflow.

GitHub pull request notifications in Slack

Route each repository to the right Slack channel, keep one living thread per PR, and mention mapped reviewers.

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