ForgeRelay

Guides How-to

Direct-to-main stays visible — without a push spam firehose.

Commit digest routes post one filtered digest per push to a watched branch in Slack or Discord.

Start free Read docs

How it works

Four steps from connection to a useful conversation.

  1. 1

    Add a Commits route for the repository and destination channel (separate from review routes).

  2. 2

    Filter by branch (for example main), suppress bots, and optionally limit conventional commit types.

  3. 3

    Confirm Contents: read / Push subscription is accepted on GitHub so digests can resolve compare links.

  4. 4

    Leave review activity on its own route so PR or MR threads stay separate from digests.

FAQ

Questions people ask before connecting.

No. Digests only post when a Commits route matches. Pushes without a matching route are ignored.

GitHub requires it to subscribe to Push events and resolve compare or commit links. ForgeRelay does not clone repositories or store your source tree.

Yes. Destinations are independent — create a Commits route for each channel you want notified.

Keep learning

Related guides for this workflow.

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

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