docs(access-control): footnote first-branch admin requirement for git flow#46473
Merged
Merged
Conversation
…less flow Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
6 Skipped Deployments
|
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
github-actions
Bot
added
the
documentation
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThis PR updates the access control guide to add footnote ChangesAccess Control Documentation
Sequence Diagram(s)sequenceDiagram
participant AccessControlDoc
participant Reviewer
AccessControlDoc->>Reviewer: add footnote reference `[^8]` to Development Branches → Create
AccessControlDoc->>Reviewer: add `[^8]` footnote text explaining one-time registration requirement
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 0
♻️ Duplicate comments (1)
apps/docs/content/guides/platform/access-control.mdx (1)
285-285:⚠️ Potential issue | 🟠 Major | ⚡ Quick winCI blocker:
supa-mdx-lintfails ongitlessspelling at Line 285.This PR is currently not mergeable because docs lint fails on this exact word. Please replace
gitlesswith lint-safe wording (e.g., “dashboard branching without a Git provider”) or add an allowed-term exception used by this docs lint setup.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@apps/docs/content/guides/platform/access-control.mdx` at line 285, The term "gitless" in the footnote text "gitless dashboard branching" is flagged by supa-mdx-lint; update that phrase by replacing "gitless" with lint-safe wording such as "dashboard branching without a Git provider" in the footnote sentence (the text starting "For gitless dashboard branching, the first branch creation...") or alternatively add "gitless" to the docs lint allowed-terms list used by your MDX linter; edit the footnote string in apps/docs/content/guides/platform/access-control.mdx (the footnote beginning with "For gitless dashboard branching") to apply the replacement or implement the allowed-term exception.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Duplicate comments:
In `@apps/docs/content/guides/platform/access-control.mdx`:
- Line 285: The term "gitless" in the footnote text "gitless dashboard
branching" is flagged by supa-mdx-lint; update that phrase by replacing
"gitless" with lint-safe wording such as "dashboard branching without a Git
provider" in the footnote sentence (the text starting "For gitless dashboard
branching, the first branch creation...") or alternatively add "gitless" to the
docs lint allowed-terms list used by your MDX linter; edit the footnote string
in apps/docs/content/guides/platform/access-control.mdx (the footnote beginning
with "For gitless dashboard branching") to apply the replacement or implement
the allowed-term exception.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI (base), Organization UI (inherited)
Review profile: CHILL
Plan: Pro
Run ID: e912aa5d-83f9-4671-89d0-b2ad7f88f1a3
📒 Files selected for processing (1)
apps/docs/content/guides/platform/access-control.mdx
…pa-mdx-lint dictionary Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
|
Actionable comments posted: 0 |
ChrisChinchilla
requested changes
May 29, 2026
Contributor
ChrisChinchilla
left a comment
ChrisChinchilla
left a comment
There was a problem hiding this comment.
Tiny tiny grammar fix
Co-authored-by: Chris Chinchilla <chris@chrischinchilla.com>
Contributor
Author
|
was late to review this, apologies Chris! Thanks for the fix suggestion. Change accepted! |
ChrisChinchilla
approved these changes
Jun 3, 2026
Contributor
Braintrust eval report
|
tomaspozo
pushed a commit
that referenced
this pull request
Jun 4, 2026
… flow (#46473) ## 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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I have read the 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
Summary by CodeRabbit