Auto-enable GitHub Pages from the deploy workflow - #2
Open
ideaclaw wants to merge 1 commit into
Open
Conversation
The deploy run on main failed at configure-pages because the repository does not have Pages enabled yet. Setting enablement: true lets the workflow create the Pages site (build type: workflow) on first run instead of requiring a manual Settings -> Pages step. Co-authored-by: ideaclaw <ideaclaw@users.noreply.github.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
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
2 participants
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.
Summary
The first deploy run on
main(after #1 merged) built and verified the static export successfully, but failed at the Configure GitHub Pages step withGet Pages site failed ... Not Found— the repository doesn't have GitHub Pages enabled yet.This sets
enablement: trueonactions/configure-pages@v5, which lets the workflow create the Pages site (build type: GitHub Actions) on its first run instead of requiring the manual Settings → Pages → Source: GitHub Actions step.After merging
mainre-triggers the deploy workflow; it should go green and publish the site tohttps://ideaclaw.github.io/tokenbrews/.tokenbrews.comand add the Cloudflare DNS records from the README (fourArecords for@pointing at the GitHub Pages IPs, plusCNAME www → ideaclaw.github.io, DNS-only while GitHub validates). Then enable Enforce HTTPS once the certificate is issued.Note: until the custom domain is attached, the
github.io/tokenbrews/project URL will render unstyled because the export uses root-absolute asset paths (/assets/...). That's expected — the site is built to be served from a domain root, which is exactly what the custom domain gives you.