-
Notifications
You must be signed in to change notification settings - Fork 902
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
CI: only run scheduled jobs on the main repo #3251
CI: only run scheduled jobs on the main repo #3251
Conversation
[pull] main from geopandas:main
This reverts commit c61c3a6.
Is there a way to run the scheduled tests only on geopandas/geopandas? I am not sure if the |
https://github.com/orgs/community/discussions/26684 might be relevant In the job itself you can detect that it was scheduled (https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#schedule), and so that way we can use the |
This reverts commit d4ed9eb.
Thanks both for the suggestions that's much cleaner |
This was inspired by the versioneer change to not run on forks. I would quite like to be able to run tests on my fork, but not have the scheduled tests trigger every day (and generate daily notifications when the dev build is broken). Currently I work around this by turning the tests workflow on and off globally under the actions tab:
Splitting the workflow conditions means these could be turned on and off individually. Happy though if we decide it's not worth the complexity - I had a quick look and can't see other projects doing this, so perhaps this is only an annoyance for me.