ForgeRelay
Use cases

Built for the team you have.

The routing model is the same for everyone. What changes is the recipe: which events a route relays, which features it overrides, and where the conversation lands.

Small engineering teams

Sophisticated review workflow without enterprise minimums.

Three to eight engineers, one busy repository, and nobody whose job it is to chase reviews. Pricing is per workspace, so a small team gets the whole routing model rather than a cut-down tier. Mix pull request routes with an optional commit route when hotfixes land on main.

  • One thread per request, so the channel keeps one line per PR
  • Mention mapped reviewers on review_requested
  • Stale review reminder after the workspace delay (four hours by default)

Route recipe

northwind/api rt_01 #eng-reviews

Review essentials preset: opened through merged, including review outcomes.

A review request reaches the person by name, and the thread closes itself when #482 merges.

route rt_01

Direct-to-main visibility

Ship without a pull request — still show up in chat.

Solo projects and light-process teams often push straight to main. A Commits route posts one filtered digest per push so Discord or Slack stays honest without a firehose.

  • Commit digests — pushes without a matching route are ignored
  • Branch filter: main only
  • Suppress bots; keep feat and fix conventional types
  • One digest per push with a compare link

Route recipe

northwind/api rt_05 #shipped

Subject: Commits · branch = main · bots off · types feat, fix.

Reviews stay in threads. Direct-to-main stays visible — three conventional commits land as one digest in #shipped.

route rt_05

Platform / DevOps teams

Pipeline failures and the recovery, in one place.

Platform work lives and dies on pipeline signal. A dedicated deploy channel carries merge request activity plus MR pipeline status, so a red main branch is visible immediately. Optional main-branch digests cover direct pushes alongside pipelines.

  • MR pipeline status: failures and recovery
  • Post into the existing MR thread, with failed jobs and duration
  • Include link to the forge and branch/SHA
  • Conditions: branch = main only

Route recipe

platform/edge rt_04 #deploys

Pipeline monitoring preset with merge request lifecycle attached.

integration-tests and lint fail on !77, then the recovery lands in the same thread three minutes later.

route rt_04

Agencies and consultancies

One relay per client, without leaking context.

Client work means separate repositories, separate channels, and often separate chat platforms. Routes are per repository-to-destination pairing, so nothing crosses over.

  • Compact messages for client channels
  • Relay top-level comments off
  • Stale reminders enabled only on the routes that need them

Route recipe

northwind/api rt_03 #deploys

Client-facing route: merges and check failures only, compact messages on.

Clients see progress on their own repository, and internal review chatter stays in the internal channel.

route rt_03

Open-source maintainers

Contributor pull requests that do not sit unread.

Maintainers cannot watch a repository all day. Conditions keep bots out, and reminders surface the contributor PR that has been waiting since yesterday. Occasional direct commits can use the same bot-suppress discipline on a Commits route.

  • Conditions: author ≠ dependabot, label ≠ wip
  • Include diff summary so triage happens in chat
  • Stale review reminder after the workspace delay (four hours by default)

Route recipe

platform/edge rt_02 #eng-reviews

Full merge request lifecycle with comment relay for first-time contributors.

A contributor gets a first response the same day, and the thread carries the whole review to merge.

route rt_02

Put the review where the team already is.

Free for up to 3 mapped people. Unlimited repos and notifications. No credit card.

Start free Explore the product