ci: announce release outcome to DingTalk - #17
Draft
Fiona2016 wants to merge 1 commit into
Draft
Conversation
Add success and failure notification steps to the publish job, matching the other SDK repositories. Success is sent to both the original and the second DingTalk robot; failure is sent to the original robot only.
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.
These release workflows had no DingTalk notification at all, so a successful or failed release went unannounced. This adds the same notification steps the other SDK repositories already use.
DING_TALK_TOKEN/DING_TALK_SECRET) and a second one (DING_TALK_TOKEN_2/DING_TALK_SECRET_2).Important
Draft until
DING_TALK_TOKENandDING_TALK_SECRETare configured on this repository.DING_TALK_TOKEN_2/DING_TALK_SECRET_2are already set; the original robot's credentials are not, and merging before they exist would make the release job fail on the notification step.