Angada/Docs
Workflows

Route a repo to a channel

Send a connected repo's notifications to a specific Slack channel.

Every connected repo posts to your Workspace's default channel unless you give it its own route. Routing is per repo — it doesn't change GitHub access, only where that repo's Slack messages land. See Connections & routing for the concept.

Steps

  1. Open Routing (/repos). Each repo row shows its current channel as a pill — an unrouted repo shows the default channel, marked as default.
  2. On the repo you want to change, use the row's add-channel control to open the channel picker, search for the channel, and select it. The repo now posts to that channel instead of (or in addition to) the default.
  3. To route several repos at once, select them with the checkboxes, then use the bulk action bar's Route action — choose a channel and whether to add it alongside existing routes or replace them.

To remove a custom route, use the pill's remove action on that repo's row; it falls back to the default channel automatically. Changing the Workspace's default channel itself (rather than one repo's route) is a separate action — see Connections & routing.

Screenshots needed

  1. The Routing page (/repos) showing a mix of default and custom-routed repo pills.
  2. The channel picker open on one repo row, mid-search.
  3. The bulk Route dialog with a few repos selected.

On this page