Repository navigation
docs: clarify Vercel CI setup - #2555
Conversation
Co-authored-by: groupthinking <154503486+groupthinking@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
✅ E2E Test Results: ALL TESTS PASSED
Test Output |
✅ E2E Test Results: ALL TESTS PASSED
Test Output |
✅ E2E Test Results: ALL TESTS PASSED
Test Output |
There was a problem hiding this comment.
🟡 Changes recommended
The manual-deploy instructions omit CLI installation and linking to garv1/v0-uvai, so vercel --prod may be unavailable or enter interactive setup on a fresh checkout.
1 open issue
What changed in this PR
Updates deployment guidance for UVAI’s web app to clarify the existing split between GitHub Actions CI and Vercel deployments, addressing #2588.
Changes:
- Replaces obsolete Actions-based deployment instructions with the current CI and Vercel Git integration flow.
- Documents PR preview discovery and the protection-bypass secret requirement.
- Warns against a second deployment path and reserves manual deployment for explicit authorization.
| File | Description |
|---|---|
apps/web/README.md |
Clarifies CI, Vercel deployments, preview access, and manual deployment guidance. |
Review effort: Max
| project's root directory and production branch in Vercel settings. Do not add | ||
| Vercel CLI deployment tokens to GitHub Actions for a second deploy path. | ||
|
|
||
| For an explicitly authorized manual deployment: |

Canonical issue
Closes #2588 (part of #2587, repo audit cleanup)
Outcome
Document the existing split: GitHub Actions runs CI checks; Vercel’s Git integration handles deployments and pull-request previews.
Scope
Risk
Verification
Production evidence
Not applicable; documentation-only change.
Agent handoff
Security dependency evidence
Not applicable; no dependency changes.