NeonN
Neon6mo ago
1 reply
progressive-amaranth

Neon branches for custom vercel environments

Hi All, there was a similar question asked about a year ago here (❓|questions-and-answersVercel Environments and Neon Branches), but I didn't see a clear answer to the question. Basically we have nearly the same workflow as the OP of the post linked above. We use preview deployments for PRs, but our default/trunk branch is called 'staging' and we merge our PRs into that, which triggers a deploy to our custom vercel staging environment. Then when we want to deploy to production, we create a staging -> main PR, and our vercel production environment is based on the 'main' branch. So my question is basically, how can I ensure that we have a 'staging' DB branch in neon that our vercel staging environment points to, and then I would like our preview branches to be based off of the staging branch not the production branch. Thank you in advance!
Was this page helpful?