Run Tests workflow only when Python changes#603
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Run Tests workflow only when Python changes
Right now the Tests workflow runs on every PR, even when the change is only docs or the OpenAPI contract or some other file that has no Python in it. Those runs can never tell us anything new, so they just waste CI time.
This adds a
pathsfilter to the workflow. Tests now run only when:**.py)requirements.txtoralembic.inichangedEverything else skips the run.
One thing to watch: if "Tests" is a required check in branch protection, a skipped run shows as pending and could block merge. If that happens we can switch to a small gate job that always reports a status. Left out for now to keep this change small.
Fixes #602