Best practice for Production / Pre-Production deployment

v0
1

When I first deployed my app using Vercel, it went straight into Production by default. Now, I want to revise my setup so I can deploy changes first to a Pre-Production environment (i.e., staging or preview), and only later push them to Production.

I’m also planning to manage this via Git, with separate branches — ideally something like:

  • main → Production
  • pre-production or staging → Pre-Production

I’ve been checking the v0/Vercel docs but couldn’t find a straightforward guide on how to configure this properly. Ideally, I’d like:

  • Git pushes to pre-production to trigger a Preview deployment
  • Git pushes to main to go to Production
  • (Bonus) A custom subdomain like staging.myapp.com to point to Pre-Production

If anyone’s already done something like this or has tips on the best setup for this kind of workflow in Vercel, I’d appreciate your insights!

Thanks in advance! :folded_hands:

2

Hi @hilmishah, welcome to the Vercel Community!

This is a really insightful post. I tried doing what you suggested and what I noticed is that v0 will always push the code to the branch you’ve set in the Production environment of your Vercel project. So, I think this flow is not yet supported. Let me talk to the v0 team to see how can we do this.

4

I think @pawlean has been suggesting a feature ‘coming soon’ that may help combat this. It is also a problem for us where we want to have development done against the code base by a developer using their IDE, directly with a github branch, which is then merged into staging and finally production.

As it currently stands, this would be overwritten by v0 without the changes on a subsequent deployment.

1 Like