mirror of
https://github.com/supabase/supabase.git
synced 2026-10-15 14:19:11 +03:00
Wen Bo Xie
626f0d412a
## Problem Users ask whether the GitHub integration applies migrations and syncs `config.toml` to a branch on its own or whether they need a GitHub Action for it but there's no docs clarifying that. The branching guides also does not have when a new branch inherits from its base project, where a dashboard branch gets its schema, what the `configure`, `migrate`, and `deploy` steps read from the repository, and what the workflow step statuses mean. ## Solution Added the missing facts to the four pages that already cover each topic, with no new pages and no moved headings. - Overview: a "What a new branch starts with" section listing the copied settings, the placeholder Auth secrets, the webhook default, and where each branch kind gets its schema. - GitHub integration: a "What runs on each push" subsection that answers the FDBKIN-11978 question directly, the `config.toml` sections the configure step applies and the protected-branch rule, two migrate edge cases and the `[db.migrations]` switch, and a new "Edge Functions" subsection on copy-from-base and checksum skips. - Dashboard: "Where a dashboard branch gets its schema". - Troubleshooting: the step status table and two new causes under "Config.toml not applying". ## Checklist Check all before review: - [x] I have read [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) - [x] If I wrote a new docs topic or edited an existing topic, I used the `/write-the-docs` or `/edit-the-docs` skill, which applies the docs [style guide](https://github.com/supabase/supabase/tree/master/apps/docs/style-guide)