Skip to content
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

Allow running cargo-generate workflow on workflow_dispatch anywhere #287

Merged
merged 2 commits into from
Aug 29, 2024

Conversation

BD103
Copy link
Member

@BD103 BD103 commented Aug 28, 2024

cargo-generate.yaml is an automated Github Action that automatically updates the cargo-generate branch from main. 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 when main is updated on forks, but still will let developers manually call it if needed.

Copy link
Member

@janhohenheim janhohenheim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea :)

Copy link
Collaborator

@benfrankel benfrankel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, seems reasonable enough.

@benfrankel benfrankel enabled auto-merge (squash) August 29, 2024 00:05
@benfrankel benfrankel merged commit 66931a7 into TheBevyFlock:main Aug 29, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants