DOCS: Ordering of cache step in GH Action YAML example #2145
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.
In the example GitHub Action YAML provided at the bottom of https://jupyterbook.org/en/stable/publish/gh-pages.html, the caching of executable content is placed before the
jupyter-book build .
command, when there are no outputs to cache at that point. This results in a GH action log message such asRun actions/cache@v3 Cache not found for input keys: jupyter-book-cache-511116b794a1ce6b75d5156b58ce1314db3e65a10292d7e9f072cad18f7711b3
This PR places the caching step after the
jupyter-book build .
, which should result in a successful GH action log message such asRun actions/cache@v3 Cache Size: ~1 MB (1110285 B) /usr/bin/tar -xf /home/runner/work/_temp/21854ee6-0f37-4c55-9aa7-0f64d703126c/cache.tzst -P -C /home/runner/work/czi-catalystproject.github.io/czi-catalystproject.github.io --use-compress-program unzstd Cache restored successfully Cache restored from key: jupyter-book-cache-511116b794a1ce6b75d5156b58ce1314db3e65a10292d7e9f072cad18f7711b3