[ ] Include unit tests for new functions and classes.
[ ] Defensive data quality/sanity checks in analyses & data processing functions.
[ ] Update the release notes and reference reference the PR and related issues.
[ ] Do your own explanatory review of the PR to help the reviewer understand what's going on and identify issues preemptively.
Issue #2461 : Have nightly builds output cache keys when successful
Enhancement: Add Nightly Builds Output Cache Keys
This pull request aims to enhance the workflow for handling Nightly Builds Output in our repository by introducing cache keys. The goal is to optimize the downloading process and reduce unnecessary downloads of the PUDL DB.
Changes Made:
Added cache-checking logic to determine if the cache is up to date.
Calculated the SHA256 hash of the downloaded PUDL DB.
Compared the cached SHA256 hash with the hash of the downloaded DB to decide whether to download a new DB.
Incorporated the latest download logic for the PUDL DB.
Why This Enhancement:
The introduction of cache keys improves the efficiency of the CI workflow by only downloading a new PUDL DB when necessary. This change can significantly speed up the CI process and save resources by avoiding redundant downloads.
Please review this pull request, and your feedback and suggestions are welcome.
PR Overview
PR Checklist
dev
).Issue #2461 : Have nightly builds output cache keys when successful
Enhancement: Add Nightly Builds Output Cache Keys
This pull request aims to enhance the workflow for handling Nightly Builds Output in our repository by introducing cache keys. The goal is to optimize the downloading process and reduce unnecessary downloads of the PUDL DB.
Changes Made:
Why This Enhancement: The introduction of cache keys improves the efficiency of the CI workflow by only downloading a new PUDL DB when necessary. This change can significantly speed up the CI process and save resources by avoiding redundant downloads.
Please review this pull request, and your feedback and suggestions are welcome.