Record the Cloudflare deploy path in the README - #16
Merged
Merged
Conversation
Cloudflare ships this Worker from the connected repo, so a push to master deploys. Nothing in GitHub Actions deploys, and the repo holds no Cloudflare API token. Calls out the one setting that fails silently: VITE_SITE_URL must be a build variable in the Cloudflare project. Vite inlines it at build time, so a value set only in GitHub Actions never reaches the deployed bundle, and the build still passes.
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
error-wolf | 1dccd96 | Jul 31 2026, 03:04 AM |
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.
Documents how this repo ships now: Cloudflare builds and deploys the Worker
from the connected repo, a push to
masterdeploys, and nothing in GitHubActions deploys.
Calls out the one setting that fails silently —
VITE_SITE_URLhas to be abuild variable in the Cloudflare project. Vite inlines it at build time, so
a value set only in GitHub Actions never reaches the deployed bundle and the
build still passes.
Merging this also serves as the deploy trigger for the newly set
VITE_SITE_URL, so the deployed bundle picks it up.Also confirms the
main-rulesetfix: the ruleset now targetsrefs/heads/masterinstead of
~ALL, so feature branches take follow-up commits again. This branchwas pushed twice to verify it.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Greptile Summary
Documents the repository’s Cloudflare deployment process.
masterdeploy through Cloudflare’s Git integration rather than GitHub Actions.VITE_SITE_URLmust be configured as a Cloudflare build variable because Vite inlines it during the build.Confidence Score: 5/5
The documentation-only change appears safe to merge.
The documented deployment path and build-variable requirements match the repository’s workflows and Vite environment-variable usage, with no actionable defects identified.
Important Files Changed
Reviews (1): Last reviewed commit: "docs: record the Cloudflare deploy path ..." | Re-trigger Greptile