Skip to content

ci: add Vercel auto-deploy via GitHub Actions#2

Merged
costajohnt merged 1 commit into
mainfrom
ci/vercel-auto-deploy
May 6, 2026
Merged

ci: add Vercel auto-deploy via GitHub Actions#2
costajohnt merged 1 commit into
mainfrom
ci/vercel-auto-deploy

Conversation

@costajohnt
Copy link
Copy Markdown
Owner

Summary

  • Vercel↔GitHub OAuth integration was severed at the account level (no Login Connection on the Vercel account, zero entries from /git-namespaces?provider=github). Restoring it requires a browser consent flow that can't be automated.
  • This workflow replaces the need for that integration: GitHub Actions runs vercel deploy --prod on every push to main, using a dedicated CI token. Push-on-commit auto-deploy without depending on Vercel's GitHub App.
  • Resilient to future integration breaks (drift, revocations, account moves).

Secrets configured

  • VERCEL_TOKEN — dedicated CI token (vcp_...)
  • VERCEL_ORG_IDteam_k7yYSWA5I9xeko4fJoU4zvpc
  • VERCEL_PROJECT_IDprj_sHqebApxx9oTVikpSjAO51uclFpb

Test plan

  • Merge → workflow fires on the merge commit
  • Verify deploy at vercel ls shows a fresh production deployment
  • Hit /api/card/costajohnt?cache=no and confirm 114 PRs / 36 repos still serving
  • Future commits on main deploy automatically without a manual step

The Vercel→GitHub OAuth integration is severed at the account level and
can only be restored through a browser consent flow. This workflow gives
us push-on-commit auto-deploy without depending on the integration:
GitHub Actions runs `vercel deploy --prod` on every push to main using a
dedicated CI token. Survives future integration breaks.

Required secrets: VERCEL_TOKEN, VERCEL_ORG_ID, VERCEL_PROJECT_ID.
@costajohnt costajohnt merged commit cb9881b into main May 6, 2026
4 checks passed
@costajohnt costajohnt deleted the ci/vercel-auto-deploy branch May 6, 2026 22:55
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