-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change behaviour of NO_PUSH to be boolean #107
Merged
Merged
Conversation
This file contains 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
Previously, any string passed to INPUT_NO_PUSH would prevent pushing. We change this to expect boolean input and provide an informative error message if true or false is not provided.
Thanks for submitting your first pull request! You are awesome! 🤗 |
sgibson91
commented
Nov 28, 2023
2 tasks
…tion into boolean-no-push
minrk
approved these changes
Dec 4, 2023
sgibson91
added a commit
to sgibson91/hub-user-image-template
that referenced
this pull request
Dec 7, 2023
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 have been trying to use this variable in GitHub Actions like so:
i.e. a build triggered by a PR would not be pushed to a registry, but a build triggered by a push to main (or whatever other events are configured by the workflow) would be pushed, which I believe is a pretty common use case.
I was surprised that this didn't work and my builds were never pushed to a registry on either trigger, and I realised this is because the action only checks if
NO_PUSH
is not empty rather than treating it like a boolean. The only way to get the desired behaviour (without this PR or some other change) would be to have two workflow files that are identical other than the one triggered by a PR hasNO_PUSH
set. You can see this in thebuild.yaml
andtest.yaml
files here: https://github.com/2i2c-org/hub-user-image-template/tree/main/.github/workflowsThis PR changes the behaviour of
NO_PUSH
to be more boolean and allows us to achieve the desired workflow in a single workflow file and without duplicating code.