From the source
Supabase has supported database branching through a git-based workflow since Launch Week X .
That workflow connects your GitHub repo to Supabase, tracks migrations in version control, and creates preview branches automatically when you open a pull request.
It works well for teams that manage their database schema as code.
But it requires a GitHub connection, which rules out anyone who doesn't work that way.
Branching 2.0 removed that requirement.
You create a branch from the dashboard, make changes using the SQL Editor or Table Editor, review a schema diff, and merge.
No git configuration required.
It shipped behind a feature preview.
Today, that preview is gone.
Branching without Git is on by default for every project.
It adds a second path for developers who want to iterate on their schema without setting up a Git integration.
Both approaches are fully supported, and you can switch between them or use them together.
If you're already using git-based branching, nothing changes.
Two ways to branch # Branching without Git Create branches directly from the Supabase Dashboard.
