Update GitHub Pages workflow example #1704
Open
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.
I've updated the GitHub Pages workflow example to use actions for the actual deployment and to set
--pathprefix
.I've also change how the caching works as I don't think the previous example would have worked correctly for most use cases. You can't change the contents of an existing cache so if you keep on reusing the same cache key then you'll eventually end up with a saved
.cache
folder that only contains stale entries.I think it would be more useful to restore the cache saved from the last run so I've changed the cache action to use a key based on the current timestamp so it will always create a new cache on each run. This means there will never be a direct cache hit on subsequent runs, but I've also set
restore-keys
so it will restore the last saved cache (from the same branch) on a miss.I'm quite new to GitHub actions so maybe there is a more elegant way to achieve this behaviour!