mirror of
https://github.com/supabase/supabase.git
synced 2026-10-10 11:55:05 +03:00
19e6e17257
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? Docs update ## What is the current behavior? The access-control permissions matrix shows Developer-role users can create development branches, but doesn't mention the implicit production-branch registration step that runs on the first "Create branch" click for a gitless project — which is Owner/Administrator only. Customers reading the matrix conclude Developers can branch from the start; in reality, an Owner/Administrator has to perform the first branch creation to register the production branch. ## What is the new behavior? Adds a footnote on the "Development Branches → Create" row that flags the one-time first-branch admin requirement and links to the dashboard branching guide for the full explanation. Short cross-link only — long-form mechanism explanation lives on the dashboard branching guide (companion PR #46471). ## Additional context - Companion PR adding the long-form admonition on the branching guide page: #46471 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Clarified branching permissions for dashboard (gitless) workflows: the first branch creation (one-time) without a GitHub integration requires Owner or Administrator to register the production branch; after that initial step, Developers may create, update, and delete branches as normal. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: Chris Chinchilla <chris@chrischinchilla.com>