lywsvip/supabase
1
0
Fork 0
mirror of https://github.com/supabase/supabase.git synced 2026-06-20 00:27:21 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: Update troubleshooting guide for production branch changes (#41534)

Browse Source 
* Update troubleshooting guide for production branch changes

Clarified the process for changing the production branch and linked to the integrations page. The previous message made it seem that you cannot change the production branch you can link to in GitHub

* Update apps/docs/content/guides/deployment/branching/troubleshooting.mdx

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This commit is contained in:
Aaron Byrne
2026-01-13 10:38:09 +07:00
committed by GitHub
parent f5d125220d
commit bdfae403f7
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
apps/docs/content/guides/deployment/branching/troubleshooting.mdx
View File

@@ -45,7 +45,7 @@ These conflicts can be resolved in the same way as normal Git Conflicts: merge o
### Changing production branch
It's not possible to change the Git branch used as the Production branch for Supabase Branching. The only way to change it is to disable and re-enable branching. See [Disable Branching](#disable-branching).
You cannot change which project branch serves as the production branch — the base project that all branches are created from will always remain the production branch. However, you can update which GitHub branch is linked to your production branch. To do this, go to the [Integrations page](/dashboard/project/_/settings/integrations) and change the production branch name.
## Migration issues