Description
Currently there is no remote preview URL for pull requests — reviewing a change requires running the local dev/preview server (npm run dev / npm run preview) on the machine doing the work. Set up Cloudflare's preview deployment mechanism (via wrangler in CI, or Cloudflare's native Workers/Pages preview-per-branch feature, whichever fits the Workers-with-static-assets deployment model this project uses — see PROJECT.md, Environmental Conditions) so each pull request gets a real, shareable preview URL.
This is a stand-in requirement until it's built: the local dev server is started after every change instead, per the working agreement.
Acceptance Criteria
- Given a pull request is opened or updated against
main, when CI runs, then a preview deployment is created (or updated) on Cloudflare and its URL is posted to the PR (e.g. as a comment or check).
- Given the preview deployment exists, when the underlying secrets/bindings it needs are unavailable (e.g. Gmail OAuth credentials not yet provisioned), then the preview still deploys successfully for static/non-dependent routes, failing gracefully rather than breaking the whole preview for functionality that isn't wired up yet.
Description
Currently there is no remote preview URL for pull requests — reviewing a change requires running the local dev/preview server (
npm run dev/npm run preview) on the machine doing the work. Set up Cloudflare's preview deployment mechanism (viawranglerin CI, or Cloudflare's native Workers/Pages preview-per-branch feature, whichever fits the Workers-with-static-assets deployment model this project uses — see PROJECT.md, Environmental Conditions) so each pull request gets a real, shareable preview URL.This is a stand-in requirement until it's built: the local dev server is started after every change instead, per the working agreement.
Acceptance Criteria
main, when CI runs, then a preview deployment is created (or updated) on Cloudflare and its URL is posted to the PR (e.g. as a comment or check).