Manually trigger builds #598
Open
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
# for free
to join this conversation on GitHub.
Already have an account?
# 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 noticed in #519 (comment) that @philippnurullin mentioned the build generated by the merged PR would only be available on the next push (that changes sources/*).
I wanted to use the variable web fonts right away, so I added
workflow_dispatchto the list of events the build is triggered by. This should give the owner of the repository the ability to manually trigger a build from the GitHub Actions UI. @philippnurullin could use it to verify the generated files are correct rather than waiting for the next change to sources/*, and the artifact would have shown up in the Actions log for curious and impatient sleuths like me. 😅I successfully used it in my own fork to manually trigger the build I wanted manually and generate the artifacts without making changes to sources/*.