Does promoting a deployment to Production from Vercel ever update or merge code into the GitHub main branch automatically, or does it only deploy an existing commit without changing GitHub branch history?
Great question! Promoting a deployment to Production in Vercel does not automatically update or merge any code into your GitHub main branch.
When you promote a deployment, Vercel simply reassigns your production domains to point to that specific deployment - it’s changing which already-built version of your site serves production traffic. Your GitHub repository and branch history remain completely unchanged.
Think of it this way:
- Deploying = Building your code and hosting it on Vercel
- Promoting = Choosing which already-built version serves your production domains
If you have code on a feature branch that you’ve promoted to production and want to also update your main branch, you’ll need to create and merge a pull request through GitHub separately. This keeps your deployment process and your Git workflow independent, giving you more control over both.
One quick issue I’m facing: the Pull Request option in v0 is taking a very long time to load, and in many cases the PR button doesn’t appear at all.
Because of this, I’m often unable to open a PR directly from v0 and have to rely on GitHub manually.
Is this expected behavior, or is there something I need to configure to make PR creation more reliable in v0?