# Supabase — How a new branch gets its config, migrations, and functions

- Company: Supabase (supabase.com)
- Announced: 2026-10-15
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://supabase.com/blog/how-a-new-branch-gets-its-config-migrations-and-functions
- Record: https://forck.live/items/23134-how-a-new-branch-gets-its-config-migrations-and-functions
- Subject: Supabase

Supabase branches are separate projects that require settings, schema, and edge functions to be in place before use. These three components are run mostly in parallel when a branch is created. Configuration copies the main project's settings, migrations provide the database schema, and function deployment copies or deploys Edge Functions.

## Evidence

Verbatim from https://supabase.com/blog/how-a-new-branch-gets-its-config-migrations-and-functions:

> Supabase branches are their own projects, so three things have to land on one before you can use it: settings, schema, and edge functions. We run all three mostly in parallel when you create the branch.

---

Record: https://forck.live/items/23134-how-a-new-branch-gets-its-config-migrations-and-functions
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md