Notify Feishu after Drone release results - #803
Merged
Conversation
yaojin3616
marked this pull request as ready for review
July 28, 2026 14:07
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
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 changed
code: 0result.FEISHU_DEPLOY_WEBHOOKDrone repository secret instead of committing the credential.Why
Production deployments currently finish without proactively notifying the team. This reports both verified success and failures from any stage of the tag release pipeline.
Validation
drone lint --trusted .github/drone.ymlgit diff --checkRequired Drone configuration
Add the supplied webhook URL as the
FEISHU_DEPLOY_WEBHOOKrepository secret before the next release tag. The Drone web session available during implementation was not authenticated, so the secret was intentionally not written through the UI or committed to Git.