Update CI workflows to run pytests and black only for changes in the backend directory #224 #233
Conversation
This file contains 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
…backend directory
|
|
amoghjalan
approved these changes
May 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #224
This PR addresses issue #224 by updating the GitHub Actions workflows to trigger the Python-centric tests (pytests and black) only when there are changes in the 'backend' directory. Previously, these workflows were running for all pull requests, which could be unnecessary for changes that don't affect the Python code (like updates to the web-server).
This optimization reduces unnecessary CI runs, speeding up development and reducing resource usage. Changes include:
.github/workflows/pytest.ymlto add path filters..github/workflows/black.ymlsimilarly.This should streamline the development process for contributors focusing on the TypeScript/Next.js portions of the project by not running Python-specific checks on unrelated PRs.