Split release into per-target workflows with individual badges#4
Merged
Conversation
GitHub Actions badges only work at the workflow level, not per-job. To show per-platform build status, split the monolithic release.yml into 5 separate workflows (one per build target). Each workflow builds its target and uploads directly to the GitHub release.
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.
Summary
release.ymlinto 5 separate workflows, one per build target (Linux x86_64, Linux aarch64, macOS x86_64, macOS aarch64, Windows x86_64)softprops/action-gh-releaseWhy
GitHub Actions badges only work at the workflow level — there's no way to get per-job badges from a single workflow. Splitting into separate workflows gives each platform its own badge.
Test plan
gh workflow listafter merge)