Repository navigation
build(ci): rebuild Pages daily so scheduled posts go live - #42
Merged
Merged
Conversation
This was referenced Nov 1, 2026
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.
GitHub Pages only builds when
masterchanges, andfuture: falsedrops future-dated posts at build time. The result is that a post scheduled for next Tuesday is invisible until some unrelated push happens to rebuild the site.This adds a daily (06:15 UTC) rebuild via the Pages build API, plus
workflow_dispatchfor manual runs. Future-dated posts now go live within a day of theirdatewithout a merge on the day.GITHUB_TOKENwithpages: write; no secrets or third-party actions.gh workflow run pages-refresh.yml.