Skip to content

ci(frontend): add Vercel config for fork PR web previews - #140

Merged
gac0812 merged 2 commits into
1024XEngineer:MVPfrom
gac0812:codex/ci-vercel-pr-preview
Aug 1, 2026
Merged

ci(frontend): add Vercel config for fork PR web previews#140
gac0812 merged 2 commits into
1024XEngineer:MVPfrom
gac0812:codex/ci-vercel-pr-preview

Conversation

@gac0812

@gac0812 gac0812 commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add frontend/vercel.json for Expo web static export on Vercel
  • Document one-time Vercel project setup so fork PRs can get Preview URLs
  • Note preview env vars in .env.example

Why

GitHub Pages preview only runs for same-repository branches. Fork PRs are skipped by design. Vercel can safely build fork PR previews without granting write credentials to untrusted workflows.

Test plan

  • Confirm cd frontend && npx expo export --platform web succeeds
  • Org admin imports the repo on Vercel with Root Directory frontend
  • Set Preview env: EXPO_PUBLIC_USE_FAKE_WS=true, EXPO_PUBLIC_WS_URL=
  • Enable fork PR deployments in Vercel Git settings
  • Open a fork PR and verify Vercel posts a Preview URL comment

Enable static Expo web exports on Vercel so pull requests from forks can get preview URLs without granting gh-pages write access to untrusted workflows.

Co-authored-by: Cursor <cursoragent@cursor.com>

@fennoai fennoai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I found three deployment issues that should be addressed before relying on this as the fork-PR preview path. The Expo production export itself completes successfully.

View job run

Comment thread README.md Outdated
Comment thread README.md Outdated
Comment thread README.md Outdated
Address preview review: allow explicit EXPO_PUBLIC_USE_FAKE_WS in production exports, document Git Fork Protection authorization, and move CI/engines to Node 22 before the Node 20 build sunset.

Co-authored-by: Cursor <cursoragent@cursor.com>
@vercel

vercel Bot commented Aug 1, 2026

Copy link
Copy Markdown

Someone is attempting to deploy a commit to the gexs Team on Vercel.

A member of the Team first needs to authorize it.

@vercel

vercel Bot commented Aug 1, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
timeflow Ready Ready Preview Aug 1, 2026 7:21am

@gac0812
gac0812 merged commit fbbe580 into 1024XEngineer:MVP Aug 1, 2026
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant