Route Slack notifications to the right team channel using CODEOWNERS
H
Henna Abbas
In monorepos where multiple teams share a single CircleCI project, sending all notifications to one shared channel creates noise for everyone. We'd like CircleCI to support routing Slack notifications based on the repository's CODEOWNERS file — so the team that owns the files that changed gets notified, not everyone.
How it would work:
When a pipeline is triggered by a commit, CircleCI looks at the changed files, resolves ownership via CODEOWNERS, and routes the notification to the mapped team's Slack channel.Why CODEOWNERS?
Most teams already maintain a CODEOWNERS file for code review purposes. Reusing it for notification routing means no duplicate configuration to manage.Things we'd want:
- A way to map CODEOWNERS team names to Slack channel IDs
- A configurable fallback channel for commits that don't match any CODEOWNERS entry
Who this helps:
Engineering teams in monorepos who want failure alerts to go directly to the team responsible for the changed code, without manual triage or a noisy shared channel.Who this helps:
Engineering teams in monorepos who want failure alerts to go directly to the team responsible, without manual triage or a noisy shared channel.