You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a tracking issue for Cloudflare Pages preview setup for PR #78 (ci: Cloudflare Pages previews). It is not blocking main or the MVP foundation — main is stable after PR #85 (merge commit 251140c).
The PR itself is well-built: the workflow YAML is correct, security controls are in place (fork guard, persist-credentials: false, minimal permissions:, pnpm install --frozen-lockfile), and CI runs lint-and-test and CodeRabbit green. The only blockers are external: Cloudflare account-level setup and a stale pnpm-lock.yaml on the PR branch.
Required maintainer actions
Create the cv-builder-web Cloudflare Pages project (one-time). Either via the Cloudflare dashboard (Workers & Pages → Create application → Pages) or:
wrangler pages project create cv-builder-web
Add repo secret CLOUDFLARE_API_TOKEN — Cloudflare dashboard → My Profile → API Tokens → Create Token → use the Edit Cloudflare Pages template, scope it to the cv-builder-web project.
Confirm both secrets are visible at https://github.com/TechImmigrants/cv-builder/settings/secrets/actions (repo admin only).
After secrets are added
Ask PR ci(web-ui): Cloudflare Pages preview deploys + setup docs #78 author (Sam / Isusami) to rebase ci/cloudflare-pages-preview against current main to clear the pnpm-lock.yaml conflict. (Test-merge of the PR head against main shows this is the only conflicting file; the rest of the changes auto-merge cleanly.)
Re-run validation on the rebased PR: pnpm install --frozen-lockfile, pnpm --filter @cv-builder/web build, pnpm lint.
Confirm the deploy step is green and posts a preview URL on the PR.
Local pnpm --filter @cv-builder/web build already produces a static export; the preview workflow is a contributor-experience improvement, not a production dependency.
The web UI can be deployed through other means in the meantime.
Notes for whoever picks this up
Only the two secrets above are needed. Do not paste tokens into issues, comments, or code.
The Cloudflare account that hosts cv-builder-web should be the same one the maintainer wants associated with Pages usage (free tier is more than enough for this project).
Once the secrets are in place, ping Sam to rebase — they have been actively iterating on the PR and a rebase should be straightforward.
Context
This is a tracking issue for Cloudflare Pages preview setup for PR #78 (
ci: Cloudflare Pages previews). It is not blocking main or the MVP foundation — main is stable after PR #85 (merge commit251140c).The PR itself is well-built: the workflow YAML is correct, security controls are in place (fork guard,
persist-credentials: false, minimalpermissions:,pnpm install --frozen-lockfile), and CI runslint-and-testandCodeRabbitgreen. The only blockers are external: Cloudflare account-level setup and a stalepnpm-lock.yamlon the PR branch.Required maintainer actions
cv-builder-webCloudflare Pages project (one-time). Either via the Cloudflare dashboard (Workers & Pages → Create application → Pages) or:CLOUDFLARE_API_TOKEN— Cloudflare dashboard → My Profile → API Tokens → Create Token → use the Edit Cloudflare Pages template, scope it to thecv-builder-webproject.CLOUDFLARE_ACCOUNT_ID— Cloudflare dashboard → Workers & Pages → right sidebar (32-char hex).https://github.com/TechImmigrants/cv-builder/settings/secrets/actions(repo admin only).After secrets are added
Isusami) to rebaseci/cloudflare-pages-previewagainst currentmainto clear thepnpm-lock.yamlconflict. (Test-merge of the PR head againstmainshows this is the only conflicting file; the rest of the changes auto-merge cleanly.)pnpm install --frozen-lockfile,pnpm --filter @cv-builder/web build,pnpm lint.deploystep is green and posts a preview URL on the PR.Why this isn't urgent
pnpm --filter @cv-builder/web buildalready produces a static export; the preview workflow is a contributor-experience improvement, not a production dependency.Notes for whoever picks this up
cv-builder-webshould be the same one the maintainer wants associated with Pages usage (free tier is more than enough for this project).References
docs/REMAINING_PRS_PLAN.mddocs/POST_MERGE_VALIDATION.md