# Supabase — Faster config, migrations and functions on branches

- 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-faster-config-migrations-and-functions-on-branches
- Subject: Supabase

Supabase explains how its branching system provisions a new preview branch with configuration, database schema, and Edge Functions, mostly in parallel, within about 20 seconds median. A branch gets its inputs either from a connected GitHub repository or from the main project, depending on whether it is git-linked. The configuration step copies Postgres, Auth, Data API, Realtime, and Storage settings from the main project, then applies repo-specific overrides if a config.toml exists. Migrations are pulled from the repo or from the main project's migration history, then run as individual transactions against the branch database.

## 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-faster-config-migrations-and-functions-on-branches
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md