-
Notifications
You must be signed in to change notification settings - Fork 252
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
Don't run tests for non-code changes #884
Comments
Hey @wd60622 as it happens I've been looking gh actions recently. We can see something similar in Github docs here, which run on any matching paths. In this case it'd be: on:
pull_request:
branches: [main]
paths: '**.py'
push:
branches: [main]
paths: '**.py' Furthermore, you can add a |
Very nice @dandeandean |
What are your thoughts @juanitorduz |
The ci.yml file has a few purposes:
Running the pre-commit is fast and not much of a concern for me. Reasonable with notebooks too Separating them out into test.yml and putting this conditional filter is where my head is at. Would like to hear other thoughts on this and if there are pros and cons to this approach. |
I've merged in #886 which uses the |
Does it make sense to only run the test suite if the code has changed? If not running the tests if the case of only docstring changes is possible, is this desirable?
Something like this might be able to be done:
The text was updated successfully, but these errors were encountered: