Repository navigation
Fix GitHub Pages deployment for Hugo - #5
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changed
public/directory as a Pages artifact.actions/deploy-pagesworkflow and the requiredpages: writeandid-token: writepermissions.main, with a manualworkflow_dispatchoption.Why
The existing workflow pushed output to
gh-pageswithGITHUB_TOKEN. GitHub documents that workflow commits made withGITHUB_TOKENdo not trigger a GitHub Pages build, which left the published site stale. This workflow uses the supported Pages artifact deployment path.Required setting
Before deployment, set Settings → Pages → Build and deployment → Source to GitHub Actions.