Add setup.py to the Cache Keys for the GitHub Actions Workflow #78
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.
🗣 Description
This adds
setup.py
to the files hashed to create the cache keys used in our GitHub Actions workflow. I am intentionally not using**/setup.py
so only thesetup.py
in the root directory of the repository (which should be the base path forGITHUB_WORKSPACE
when running an Action) is used. This prevents unexpected behavior if a package contains asetup.py
.💭 Motivation and context
Since we direct requirements for our Python projects to be stored in
setup.py
we should invalidate a cache based on changes to that file. The file generally will not change much outside of requirements changes once a project is past it's initial implementation.🧪 Testing
I confirmed that in the GHA run the cache key is updated to include a hash for
setup.py
.📷 Screenshots (if appropriate)
✅ Checklist