Cypress Cloud Slack and GitHub alerts: failure-only notifications without losing flaky test visibility

Goal

Configure Cypress Cloud notifications so the team is alerted to genuine run failures in Slack and GitHub, without a message for every passing run, while still keeping flaky tests visible somewhere for triage.

Constraints and uncertainty

Alerting is configured at the organization or project level in Cypress Cloud, not per spec file, so any filter applies broadly. The GitHub integration posts commit status checks and PR comments, and the Slack integration can be scoped by run outcome and branch. The concern is that restricting Slack to failed runs on main and release branches may also silence signal from feature branches where regressions are first introduced. Separately, flaky test detection flags tests that pass and fail across runs without code changes, but it is unclear whether flake analytics remain useful if flaky specs are muted, and whether muting risks hiding real failures.

Some alerting and flake-detection capabilities appear to depend on the Cloud plan tier, so the exact filter options available may differ from what documentation describes.

Questions

1. Can Slack notifications be filtered by both branch and run outcome simultaneously, or only one dimension at a time?
2. Does muting a known-flaky spec remove it from flake analytics, or only from notifications?
3. Is there a way to keep GitHub status checks failure-only while retaining PR comments for flaky test summaries?