---
title: "Branching Without Git Is Now The Default"
description: "Supabase has made dashboard-based database branching the default for all projects, adding a GitHub-free alternative to its existing git-based workflow. Developers can create a branch from the dashboard, work in the SQL Editor or Table Editor against a separate Postgres instance, review a schema diff, and merge changes into production without Git configuration. The workflow uses pg-delta, a new schema-diffing engine in pg-toolbelt that covers tables, columns, RLS policies, functions, triggers, indexes, and extensions, replacing migra as dashboard branching’s default engine; pg-delta is alpha software and is also available in the CLI behind a flag. Git-based branching remains fully supported, and the two approaches can be switched between or used together, while branches created through the Supabase MCP server use dashboard branching automatically."
---

# Branching Without Git Is Now The Default

[Supabase](https://yomu.fyi/company/supabase) · joshenlim, qiao, saxonf · May 4, 2026

**Type:** Announcement

## Summary

Supabase has made dashboard-based database branching the default for all projects, adding a GitHub-free alternative to its existing git-based workflow. Developers can create a branch from the dashboard, work in the SQL Editor or Table Editor against a separate Postgres instance, review a schema diff, and merge changes into production without Git configuration. The workflow uses pg-delta, a new schema-diffing engine in pg-toolbelt that covers tables, columns, RLS policies, functions, triggers, indexes, and extensions, replacing migra as dashboard branching’s default engine; pg-delta is alpha software and is also available in the CLI behind a flag. Git-based branching remains fully supported, and the two approaches can be switched between or used together, while branches created through the Supabase MCP server use dashboard branching automatically.

## Context

Supabase’s earlier database branching workflow required connecting a GitHub repository, which excluded teams that do not manage database schemas through Git. Branching 2.0 adds a dashboard-based path for schema iteration without upfront Git integration, while retaining the existing git-based workflow.

## Approach / What changed

Dashboard branching creates a branch with its own Postgres instance and current production schema. Users make changes in the SQL Editor or Table Editor, review a generated migration diff, and merge the result. The diff is produced by pg-delta, which replaces migra for dashboard branching and supports a broad range of Postgres objects.

## Takeaways

- Dashboard branching is now the default for new projects and users without a configured Git integration; existing git-based branching setups continue to work.
- pg-delta compares branch and production schemas and generates migration statements for tables, columns, RLS policies, functions, triggers, indexes, and extensions.
- Branches created through the Supabase MCP server use dashboard branching automatically, allowing AI tools to create, modify, merge, and clean up branches without touching Git.

**Tags:** [Developer Experience](https://yomu.fyi/topic/developer-experience), [Migrations](https://yomu.fyi/topic/migration), [Postgres](https://yomu.fyi/topic/postgres)

- Source: [Supabase](https://supabase.com/blog/branching-without-git-is-now-the-default)
- Source URL: https://supabase.com/blog/branching-without-git-is-now-the-default
- Ingested by Yomu: 2026-08-30T00:00:58.318Z

[Read original post](https://supabase.com/blog/branching-without-git-is-now-the-default)