Branching without Git is now the default for all Supabase projects. Create a branch directly from the Supabase Dashboard, make schema changes, review the diff, and merge. No Git configuration required. Git-based branching remains fully supported for teams that manage migrations in version control. You can start with dashboard branching and add a Git integration later.
Two ways to branch
Dashboard branching (default) Create branches directly from the Supabase Dashboard. Each branch gets its own Postgres instance with your current production schema. Make changes using the SQL Editor or Table Editor, preview the diff, and merge. The whole workflow stays inside Supabase.
Git-based branching Connect a GitHub repo to your Supabase project. Migrations live in version control, and branches are created automatically when you open a pull request and cleaned up when it closes.
Key features
- No-Git workflow: Create and merge branches entirely from the dashboard. No GitHub connection needed.
- Git-based workflow: Optionally integrate with GitHub for pull request-driven schema reviews.
- Isolated environments: Each branch has its own Supabase instance with separate API credentials.
- Automatic migrations: Runs new migrations when changes are pushed to the ./supabase/migrations directory.
- Data seeding: Seed branches with sample data using ./supabase/seed.sql.
- CI/CD integration: Supports preview deployments with hosting providers like Vercel.
- Merge requests: Review schema diffs and merge changes directly in the dashboard.
When to use branching
- Developers prototyping schema changes who want fast iteration without upfront configuration
- AI agents that need to create and manage database branches programmatically
- Teams managing database migrations in Git who want PR-driven schema reviews
- Projects with complex schemas requiring careful diff review before merging
- CI/CD pipelines integrating database changes alongside application code