Allow running cargo-generate workflow on workflow_dispatch anywhere
#287
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
benfrankel
approved these changes
Aug 29, 2024
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.
cargo-generate.yamlis an automated Github Action that automatically updates thecargo-generatebranch frommain. It's proven to be a bit flaky in the past, so I've found myself testing it on my fork a lot. The issue is that this action is automatically skipped if run on a fork. This is generally good, unless you want to test the workflow specifically and are not an average user.The amend this, I made the action run if on the source repository OR if it was manually called using
workflow_dispatch. This way, it won't run whenmainis updated on forks, but still will let developers manually call it if needed.