Introducing Branching 2.0

Supabase has introduced Branching 2.0, an updated feature that allows users to create branches without the need for Git, simplifying the process for those who prefer not to use GitHub. A Supabase branch serves as a replica of a project, minus the data, enabling developers to make changes in a safe environment before merging them back into production. The previous branching system required a GitHub connection to sync database schemas, functions, and configurations, which was ideal for code-first workflows but less suitable for database-first or no-code approaches. The new system provides the flexibility to create branches through the dashboard, Supabase CLI, or Management API, and supports both Git and Gitless workflows. However, there are some current limitations, such as the inability to merge between preview branches and the need for manual conflict resolution in some scenarios. The initiative aims to eventually enable seamless transitions between different workflows, enhancing the development process by allowing users to experiment and integrate changes efficiently. The updates are currently in a feature preview phase, and feedback is encouraged for further improvements.