Conversation
furi0us333
previously approved these changes
Jun 14, 2022
kylewillmon
previously approved these changes
Jun 14, 2022
A note in the workflow_dispatch documentation states: > Note: The workflow will also receive the inputs in the > `github.event.inputs` context. The information in the `inputs` context > and `github.event.inputs` context is identical except that the > `inputs` context preserves Boolean values as Booleans instead of > converting them to strings. Making the change universally helps to simplify the understanding of how these inputs are provided and therefore how they can be used.
Contributor
Author
|
The changes made in the most recent commit have been tested and confirmed to work...at least syntactically. Confirmation on the ability to trigger the |
furi0us333
approved these changes
Jun 14, 2022
4 tasks
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.
It turns out the following syntax is invalid for a GitHub Actions workflow:
This was discovered after merging the new Docker workflow and attempting to trigger it
After searching the docs and coming up empty, a GitHub Community Forum post for this issue (but for
startswithinstead ofcontains) showed the way to go:Closes #50
Checklist
closes #<issueNum>in description above)?