Set fetch depth to 0 to pull history to fix hugo lastmod #32
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.
Proposed changes
We use Hugo Lastmod to generate
last-modified
metadata in our rendered pages, as well aslastmod
values across site maps.By default, the github checkout action only fetches at a depth of
1
, which is faster and fine for most cases. Hugo uses this to figure out the last modified date, so all metadata was being set to the current date, and therefore incorrect.For our largest repo, this add 4 seconds to our checkout time, which we can afford 😅 .
Add
enableGitInfo=true
to hugo'sconfig.toml
.Checklist
Before creating a PR, run through this checklist and mark each as complete.
CONTRIBUTING
documentREADME.md
andCHANGELOG.md
)