Slack

Slack notifications are useful when a run needs attention outside GitHub. Keep the messages short and route them to channels where the owning team can act.

When to notify

Notify Slack for failed protected journeys, degraded smoke plans, and mobile artifact handoff failures. Avoid notifying for every passing run unless the channel is dedicated to release verification.

Message content

Slack messages should include the plan, target environment, pass or fail status, evidence link, and the first actionable failure detail.

Recommended routing

• Pull request smoke failures go to the repository or product channel.
• Release candidate failures go to the release channel.
• Mobile artifact failures go to the mobile or QA channel.
• Execution health issues go to the platform or infrastructure channel.

Noise control

Start with failures only. Add passing summaries only for channels that exist specifically for release verification or audit trails.