Description:

Currently, the CircleCI Slack app only supports notifications for the default branch of a project. Teams frequently need visibility across more than one branch — for example, monitoring both main and a release branch, or a set of long-running feature branches.

What we'd like:

The ability to specify multiple branches (not just the default branch) when configuring Slack notifications at the project level in the CircleCI Slack app.

Why it matters:

Teams often have more than one branch that matters for operational visibility. Limiting notifications to a single default branch means teams either miss important failures on other key branches, or have to fall back to the Slack Orb with manual YAML configuration — which defeats the purpose of the no-config Slack app integration.

Proposed solution:

Allow users to enter one or more branch names (or branch patterns) when setting up project-level Slack notifications in the app. This could be a multi-value input field or support for wildcard/regex patterns.