Repository navigation
chore(cli): map projects, orgs, link and bootstrap command permissions - #7170
Merged
Merged
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…ayers Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
bootstrap imported it from commands/projects, which the code-structure test forbids. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
🤖 AI Review
Both independent reviews were available. Source inspection confirmed one documentation nit and refuted the other wording concern. No functional defect was established; tests were not run during adjudication.
Findings
| Severity | Location | Category | Sources | Claim |
|---|---|---|---|---|
| ⚪ NIT | apps/cli/src/commands/projects/SIDE_EFFECTS.md:85 |
documentation |
claude | The note overstates deletion's cache behavior: delete attempts a best-effort cache fill, but a project lookup returning 404 prevents any cache write. |
Refuted findings (kept for transparency, not posted as review comments)
apps/cli/src/commands/projects/SIDE_EFFECTS.md:44(documentation): The SUPABASE_PROJECT_ID row could imply that delete resolves its deletion target from supabase/.temp/project-ref, although the file is used only to decide whether to unlink.
Refuted: The row discusses the linked-project environment variable, not deletion-target resolution. The same document explicitly identifies the file's role as an 'unlink match' at line 12, consistent with the handler. Read in context, the documentation does not claim that the file supplies the deletion target.
Stats
Claude findings: 2 · Codex findings: 0 · Confirmed: 1 · Refuted: 1 · Uncertain: 0
Models: claude-opus-5-5 + gpt-6.1-sol · Trigger: auto · Workflow run
This review runs once per PR. A maintainer can request another with a /ai-review comment.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
jgoux
approved these changes
Oct 15, 2026
…on-map-projects # Conflicts: # apps/cli/tests/helpers/permission-pending-commands.ts
…on-map-projects # Conflicts: # apps/cli/tests/helpers/permission-pending-commands.ts
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.
Maps the Management API operations behind the projects, organizations and linking commands, so scoped access tokens can be given matching permissions. This changes no command behaviour.
Commands:
projects api-keys|create|delete|list,orgs create|list,link,unlink,bootstrap,services(removed from the pending list).New shared block:
organizationPicker(projects.prompt.ts): the organization listing made when no organization ID is given.Declarations
projects api-keys: the keys read, withreveal=truewhen--revealis set; the project picker and the cache fill.projects create: the create call, the organization listing (via the picker, when--interactiveallows a prompt), the cache fill.projects delete: the delete call and a project listing for its own picker (it ignores the env and.tempref, so it doesn't reuse the shared picker), the cache fill.projects list,orgs create|list: their single call;listalso fills the cache for a linked ref.link: project, API keys (reveal=true), storage and pooler reads, the branch listings, the picker, the cache fill.unlinkmakes no API calls.bootstrap: organization listing (always, since it passes no org ID), project create, API keys, health, storage and pooler reads, cache fill. The pooler read is required because the migration push depends on the pooler URL it saves on IPv4-only networks. No login call is declared: with no token the command fails before the login runs.services: the linked project's API keys and project reads (both best-effort), cache fill.Conditions:
--revealis tested by value.--interactiveis optional, so it is declared as two entries (absent, and present with "is true" in the context). Interactive-terminal, config and argument-shape prerequisites are contexts.Worth knowing
bootstrap's browser login is unreachable when no token resolves; the platform-API layer fails first.link --passwordandSUPABASE_DB_PASSWORDhave no effect.link's cache inclusion and its second branch-listing entry (a required entry for the same operation shadows them), andbootstrap's pooler entry (asserted from the handler).Docs: wrong rows corrected in the projects, bootstrap and link
SIDE_EFFECTS.mdfiles (environment variable name, create body, org listing, bootstrap request body and cache-fill attribution, the--passwordrow).🤖 Generated with Claude Code