The basic rule: code lives in GitHub, production lives on Vercel, decisions live in the README.
What you will have
- Repository with history
- Production deployment
- Environment variables checklist
- Rollback path
● Steps
Cursor to GitHub to Vercel: the clean deployment pipeline
01
Create repo
Keep commits small and readable.
02
Connect Vercel
Import the repo and keep framework settings explicit.
03
Add env vars
Never hardcode tokens, form secrets or API keys.
Common failure points
- Only having code inside Cursor
- Changing production manually
- No env var list
Deployment broken?
I can inspect the repo, Vercel logs and domain settings.
- Build fails
- Env vars missing
- Domain points nowhere