Supabase Branching 2.0: Flexible Database Experimentation Without Git

Developers and teams have long sought easier ways to test features and iterate on databases without risking production data. Supabase Branching 2.0 delivers this flexibility, empowering users to create safe, isolated environments for experimentation, no GitHub connection required. Whether you prefer a code-first workflow or a no-code approach, this update brings branching to the masses.

Why Supabase Branching Matters

A branch in Supabase acts as a clone of your project (excluding data), letting you innovate and test changes with confidence. 

You can develop new features, modify edge functions, or adjust configurations, then merge finalized changes to production, reducing risk and accelerating iteration.

What’s New in Branching 2.0?

Previously, branching in Supabase depended on integrating with a GitHub repository. Each pull request spun up a corresponding database branch, which kept code and database changes tightly synchronized. While effective for traditional development teams, this left no-code users and those focused on database management with limited options.

Branching 2.0 removes the Git requirement. You can now create and manage branches directly from the Supabase dashboard, CLI, or Management API. While Git integration remains available for teams that need it, anyone can now branch their project with a single click, no version control setup necessary. Every new branch is an instant clone of your production environment, streamlining collaboration and experimentation.

​

How Gitless Branching Works

1. Create a Branch: Name your branch and choose whether to sync with GitHub. If your main branch has migrations, these are applied; otherwise, a schema dump initializes the branch.
   
   
2. Make Changes: Use the table editor, SQL editor, or connect via your preferred tools to adjust schemas, functions, or configurations.
   
   
3. Review and Merge: Initiate a merge request from the dashboard for team review, or leverage the Supabase Assistant to validate your changes.
   
   
4. Sync With Production: Pull in the latest changes from main if your branch falls behind, keeping in mind that updates to edge functions may be overwritten.
   
   
5. Merge to Production: When ready, merge your branch with a simple click. Decide whether to delete or retain the branch for continued work.

Selecting Your Workflow

Supabase now caters to a range of teams and development styles:

• Git-based: Best for code-centric teams needing version control, file-based conflict resolution, and complex repository management.
  
  
• Gitless: Ideal for no-code, low-code, or database-first teams seeking rapid iteration and a user-friendly dashboard experience.

Current Limitations

• Custom roles created in the dashboard are not included during branch creation.
• Only public schema changes are supported at this stage.
• Database extensions are not displayed in diffs.
• Branches only merge into main; you cannot merge between preview branches.
• Function deletions require manual action on the main branch.
• Migration conflicts must be resolved manually within the preview branch.
• New branches with existing main migrations are based solely on those migrations, not a full schema dump.

Looking Ahead

Supabase is committed to supporting seamless transitions between workflows. Start with dashboard-based prototyping and shift to code-first migrations as your project matures, the platform is designed to adapt. Branching 2.0 is currently in early release and available behind a feature preview, with ongoing improvements shaped by community feedback.

How to Get Started

Opt-in to Branching 2.0 directly from the Supabase dashboard. Review the current feature limitations to ensure it fits your needs, and share your experiences to help improve the tool for everyone. The Supabase team encourages early experimentation and user feedback.

Conclusion

Branching 2.0 is a significant leap toward accessible, flexible, and collaborative database development. By decoupling from Git, Supabase broadens its appeal to all types of users, while maintaining a safe, streamlined path to production. Dive in, test new ideas, and help shape the future of Supabase branching.

Source: Supabase Blog