Fix skipped status in build notifications#62
Merged
Conversation
heifner
approved these changes
May 19, 2026
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
2 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.
Why
The Build Platforms job is optional and is expected to be skipped whenever the required builder image already exists. After PR #58, the notification action receives
build-platforms:skippedalong with successful discover/build jobs and reports the whole workflow notification as SKIPPED even though the workflow itself passed.Summary
build-platforms:skippedtosuccessonly in the notification payloadfailureandcancelledresults from the Build Platforms jobValidation
26117752616for commit0ea07e6, where the workflow concluded success but the notification action reported SKIPPED becausejob-resultsincludedbuild-platforms:skippedgit diff --check