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

Fix workflows #227

Merged
merged 2 commits into from
Oct 28, 2019
Merged

Fix workflows #227

merged 2 commits into from
Oct 28, 2019

Conversation

di
Copy link
Sponsor Member

@di di commented Oct 28, 2019

I was surprised to get a "Run failed" notification after merging #226.

This PR fixes a broken workflow, and also runs the workflows on every PR so we can see if they're broken before merging.

@di di requested a review from brettcannon October 28, 2019 19:17
@di
Copy link
Sponsor Member Author

di commented Oct 28, 2019

And of course, the checks aren't going to run here since no docs or .py files have changed.

@brettcannon What's the rationale for restricting the workflow runs like this? Any reason not to just make them run with every PR/push like Travis is currently configured?

@brettcannon
Copy link
Member

@di "What's the rationale for restricting the workflow runs like this?" If you're asking why "push" over "PR" it was to wait until they were stable enough to warrant relying on them. If you're asking why not run all steps for all PRs no matter what, I was just trying to not burn some coal somewhere for no good reason.

@di di merged commit c250bf4 into master Oct 28, 2019
@di di deleted the fix-workflows branch October 28, 2019 21:09
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.

2 participants