feat: Add a new tag indicating which step a workflow failed at#69
Merged
kenzoengineer merged 1 commit intomainfrom Aug 28, 2025
Merged
feat: Add a new tag indicating which step a workflow failed at#69kenzoengineer merged 1 commit intomainfrom
kenzoengineer merged 1 commit intomainfrom
Conversation
IanWoodard
approved these changes
Aug 26, 2025
Member
|
Would it be possible to add tests for this? |
Member
Author
Good idea, let me add in a PR |
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
3 participants
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.
Motivation
It would be useful to see which stages a pipeline fails at most often, in order to better assess its overall health.
Idea
By adding a tag that indicates the step at which a workflow fails, we can split charts by stage in Sentry. For example, one could filter by repo and then group results by failure step.
Implementation
According to the workflow job API documentation,
conclusionandstepsare required keys in the job payload, so the key accesses should never fail. Additionally, this change introduces no new behavior for pipelines that complete without error.