ForgeRelay

Guides How-to

Get GitHub pull request notifications in Slack — without the firehose.

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

Start free Read docs GitHub + Slack

How it works

Four steps from connection to a useful conversation.

  1. 1

    Connect GitHub as a source and Slack as a destination in Connections.

  2. 2

    Create a route from a repository to a Slack channel and choose the review events to relay.

  3. 3

    Map reviewers under People so requests mention real Slack users.

  4. 4

    Optionally enable one-thread-per-request, check status, and a single stale-review reminder.

FAQ

Questions people ask before connecting.

Yes. Create one route per repository-to-channel pairing — for example reviews in #eng-reviews and merges in #releases.

With One thread per request on, the first event posts in the channel and later updates for that pull request stay in its thread.

ForgeRelay falls back to the GitHub handle as plain text instead of mentioning the wrong person.

Keep learning

Related guides for this workflow.

GitHub pull request notifications in Discord

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

Read guide

Route pull requests to chat by repository or label

Use routes to separate repositories, labels, authors, branches, and review events across Slack and Discord without a notification free-for-all.

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