Repository navigation
feat(notify-pipeline-complete): support custom state and target sha - #817
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
danadajian
changed the title
|
🎉 This PR is included in version 1.91.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Adds two optional inputs to
notify-pipeline-completeso a release-train consumer can report a crashed train accurately: it marks that train's own deployment as failed, even when a newer deployment exists in the environment, and sets a failingPipeline Statuson open and queued PRs.state: the state applied to the deployment status and to thePipeline Statuscommit statuses on merge-queue SHAs and open PR head SHAs. Defaults tosuccess, so existing callers are unaffected.sha: when provided,listDeploymentsis filtered by that SHA so the deployment for that commit is marked, matchingset-deployment-status. When omitted, the newest deployment in the environment is marked as before. Commit-status targeting is unchanged.failurestate on both the merge-queue and open-PR paths, and confirmlistDeploymentsreceivesshaonly when it is provided.🤖 Generated with Claude Code