Add success notification for other release workflows #18727
Merged
Conversation
This file contains 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
Add notification for a successful release, see related PR #18661
Zelldon
force-pushed
the
ck-success-release-notify
branch
from
580c4a7
to
a1a0a02
Compare
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.
Description
Add notification for a successful release, to all releases.
Note
As the release is triggered async, we need to follow the progress of the release on GitHub. To make this easier, we send a success notification to Slack (not only for failures).
This allows us to just follow the slack channel, and do other things in the meantime (and get notified). Furthermore, we can reference back to the success message if necessary.
Related issues
related PR #18661