fix: simplify workflow boolean checks#58
Merged
Conversation
Signed-off-by: Melissa Kilby <mkilby@apple.com>
katiewasnothere
approved these changes
Dec 4, 2025
katiewasnothere
left a comment
Contributor
There was a problem hiding this comment.
Yes, the intention was to only publish tar files for the images when we aren't making a release. That way people can download the newly built builder images and test it locally if they'd like. When we're making a release, we publish the builder image to ghcr.io so it's not necessary to also publish as an artifact of the build pipeline.
|
I think it would have been much cleaner to move the build/publish steps to the calling workflows instead of keeping the conditional logic here, but that can be a future improvement. |
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.
I believe the issue was that
${{ inputs.publish }}got evaluated to a string ... and this way it follows the recommended practices more closely as well.Just to double-check: The intention is for these workflows to run when
inputs.publishisfalse? This is what it would do now, because of${{ !false }}which becomestrue. On the other hand changinginputs.publishto true:${{ !true }}becomesfalseand it will not run.CC @madrob