Skip to content
This repository was archived by the owner on May 20, 2026. It is now read-only.

ENG-1247: Notify #github-actions on workflow failure - #26

Merged
mjohnsonsu merged 2 commits into
mainfrom
chore/eng-1247-notify-slack-on-ci-failure
May 7, 2026
Merged

ENG-1247: Notify #github-actions on workflow failure#26
mjohnsonsu merged 2 commits into
mainfrom
chore/eng-1247-notify-slack-on-ci-failure

Conversation

@mjohnsonsu

Copy link
Copy Markdown
Contributor

Summary

  • Adds a notify-failure job to main.yml posting to #github-actions via SLACK_CI_WEBHOOK_URL (org-level secret) when any job fails on push to main.
  • PR-trigger failures excluded via guard.
  • No-ops cleanly if the secret isn't set.
  • Part of ENG-1247 cross-repo rollout.

Linked Linear Ticket

  • references ENG-1247

Test plan

  • Once SLACK_CI_WEBHOOK_URL org secret is set, force a failure on main and confirm the message lands in #github-actions.

🤖 Generated with Claude Code

Adds a notify-failure job that posts to Slack via SLACK_CI_WEBHOOK_URL
when any job fails on push to main. PR-trigger failures filtered via
the github.event_name != 'pull_request' guard.

Part of ENG-1247 cross-repo rollout.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Comment thread .github/workflows/main.yml Fixed
The notify-failure job only POSTs to Slack via a webhook URL — it doesn't
need any GITHUB_TOKEN scopes. Adding permissions: {} satisfies the
CodeQL actions/missing-workflow-permissions rule (GHAS "Workflow does
not contain permissions") flagged on the original PR.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Comment thread .github/workflows/main.yml
@mjohnsonsu
mjohnsonsu merged commit 9ba4152 into main May 7, 2026
8 checks passed
@mjohnsonsu
mjohnsonsu deleted the chore/eng-1247-notify-slack-on-ci-failure branch May 7, 2026 16:57
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants