Vercel + Supabase + Next. How to set up custom branching.
🌲branching
Hi all — quick question about Vercel + Supabase branching.
Current setup:
Next.js on Vercel with the Supabase integration
main → Vercel production → Supabase main
GitHub PRs create Vercel preview deployments + Supabase preview branches (works fine)
What I want:
feature → staging → main
staging should be persistently deployed
Vercel “staging” env linked to a persistent Supabase staging branch
Feature PRs merge into staging
Later PR from staging → main for release
Problem:
The Vercel–Supabase integration auto-manages env vars
I can’t manually link a persistent Supabase branch to a non-prod Vercel environment
Integration seems to assume only main (prod) + ephemeral PR previews
Question:
Is this workflow supported with the current integration?
If not, what’s the recommended approach?
Thanks!
Current setup:
Next.js on Vercel with the Supabase integration
main → Vercel production → Supabase main
GitHub PRs create Vercel preview deployments + Supabase preview branches (works fine)
What I want:
feature → staging → main
staging should be persistently deployed
Vercel “staging” env linked to a persistent Supabase staging branch
Feature PRs merge into staging
Later PR from staging → main for release
Problem:
The Vercel–Supabase integration auto-manages env vars
I can’t manually link a persistent Supabase branch to a non-prod Vercel environment
Integration seems to assume only main (prod) + ephemeral PR previews
Question:
Is this workflow supported with the current integration?
If not, what’s the recommended approach?
Thanks!
