Automate Cloudflare Pages deployment - #27
Merged
Merged
Conversation
Merges to main built GitHub Pages but left the authoritative Cloudflare Pages project unchanged, so new posts required a manual upload before appearing on gptcode.dev. Add a pinned Wrangler action to the existing validated Jekyll workflow, keep credentials in GitHub Secrets, and enforce the deployment contract with a site identity test. A future migration to Cloudflare Git integration could remove the API token, but direct-upload projects require this explicit CI deployment today.
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
1 participant
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
Validation
Security