How a new branch gets its config, migrations, and functions

Supabase branches operate as independent projects that become ready after configuration, database schema migrations, and Edge Function deployment are completed, typically in parallel and usually within about 20 seconds. GitHub-connected branches use configuration files, migrations, seeds, and functions from the associated repository branch, while gitless branches derive schema and functions from the main Supabase project. Branch setup copies most project settings, including Postgres, Auth, API, Realtime, Storage, SSL, and network controls, while excluding Auth secrets; configuration is optimized to minimize restarts and repository settings can override copied settings. Git-based workflows run sequential cloning, pulling, health checks, configuration, migrations, seeding, and deployment on each push, whereas gitless branches use a shorter pull-and-migrate process. Migrations are applied transactionally per file, preserving atomicity and detailed error reporting, while Edge Functions are copied initially and later redeployed only when their compressed bundles or JWT settings change. Workflow statuses indicate progress, warnings, successes, and failures, with dependent steps halted after critical failures, and branch logs in the dashboard provide troubleshooting details.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.