Add Slack notification for CI failures #816
Merged
+59
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this comment.
Pull Request Overview
This PR adds a Slack notification job to the CI workflow that sends alerts when builds fail on the main branch. The notification system includes a caching mechanism to prevent duplicate notifications for the same failure state.
Key changes:
- Added a new
notifyjob that triggers on failure of any dependent job - Implemented notification caching to avoid duplicate Slack messages for the same configuration
- Integrated Slack webhook notification with build status emojis
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
fnando
approved these changes
Oct 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Add a notification job to the CI workflow that sends Slack messages when builds fail on the main branch. Implement caching to prevent duplicate notifications for the same image configuration.
Why
Teams need immediate visibility into CI failures on the main branch to respond quickly to broken builds without being spammed by repeated notifications.