Skip to content

devops: Set up Slack integration for GitHub Actions CI failure notifications #663

Description

@FaveTeamz

Summary

CI failures are currently only visible in the GitHub Actions UI. Developers must check the GitHub interface proactively to know if their merge broke the build. There is no proactive notification to the team's Slack workspace.

Problem

A broken main branch can go unnoticed for hours if no one checks the GitHub Actions dashboard. This blocks other developers from merging their own PRs without knowing the build is already red.

Acceptance Criteria

  • Add a notify-slack reusable workflow that posts to a configurable Slack channel
  • Trigger on: CI failure on main branch (backend, frontend, contract CI workflows)
  • Message includes: workflow name, commit SHA (truncated), author, commit message (first line), link to failing run
  • Use a Slack Incoming Webhook URL stored in GitHub Actions secrets as SLACK_WEBHOOK_URL
  • Do not post on PR failures — only on merges to main
  • Add a green Build restored message when a previously failing build passes again
  • Document setup in docs/ci-cd.md

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programdevopsCI/CD and infrastructure

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions