Fix CI triggers: Only run Python tests when Python files change #6654
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.
This PR fixes the CI configuration to only run Python tests when Python files are changed.
Currently, the Python tests are running on all PRs, even when only frontend files are changed. This causes unnecessary CI runs and potential failures due to missing frontend dependencies in the Python test environment.
Changes:
paths
filter to the Python test workflow to only run when Python files or related files are changedopenhands/**
agenthub/**
evaluation/**
tests/**
pyproject.toml
poetry.lock
.github/workflows/py-unit-tests.yml
This change will make the CI more efficient and avoid false failures.
To run this PR locally, use the following command: