Add notification steps for build success and failure - #22
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This pull request adds automated notifications to the workflow for the
mainbranch, improving visibility into build failures and recoveries. Two new jobs have been introduced to send alerts to Discord when the build fails or when it recovers.Workflow notification enhancements:
notifyjob that triggers on build failure for themainbranch and sends a notification using the shareddiscord-notify.ymlworkflow.notify-recoveryjob that triggers on build recovery (success after failure) for themainbranch, using the sharednotify-recovery.ymlworkflow and specifying the branch asmain.