-
Notifications
You must be signed in to change notification settings - Fork 46
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
GitHub Actions #162
Comments
@corentincarton I actually use it to check the unit tests every time I push something new on any branch, instead of waiting for them to be merged in develop. However it is ok for me to limit the actions just on PR if it is annoying with many notifications. |
@doc78 , thanks. I'll work on a PR with a new version of the ci that is activated only when we are ready to merge to develop. I think running it all the time on all the branches is a waste of resources and is indeed a bit annoying as we get ci failure notifications all the time. |
@doc78, I see that the GitHub actions are running for all the branches and all the commits, which is a bit overkill. Shouldn't we run them just for the PR to develop and master? Here's an example on how it could be done:
https://github.com/ecmwf/pyflow/blob/develop/.github/workflows/ci.yml
The text was updated successfully, but these errors were encountered: