Guides How-to

Send each pull request to the conversation that can act on it.

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

Start free Read docs

How it works

Four steps from connection to a useful conversation.

1
Choose the source repository or GitLab project that should enter the route.
2
Choose the Slack or Discord destination channel owned by the team that needs the signal.
3
Add conditions such as label, author, branch, draft state, or event to keep broad activity out of focused channels.
4
Test delivery, then use the activity log to confirm the route matched the intended request.

FAQ

Yes. A repository can have separate routes for different teams, labels, branches, or event types.

Yes. Set the draft behaviour on the route so draft work stays quiet until it is ready for review.

Yes. ForgeRelay evaluates the request data supplied by each provider and shows the matching activity in the app.

Keep learning

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

Schedule a review digest for awaiting, failing, blocked, stale, or ready-to-merge work, then open the queue when something needs attention.

Keep going

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

Start free