• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

supabase / cli / 39601816826
67%
develop: 46%

Build:
Build:
LAST BUILD BRANCH: gh-readonly-queue/develop/pr-7380-74d4774766936b6e6141a58d061c3396a01c85c9
DEFAULT BRANCH: develop
Ran 21 Oct 2026 12:43PM UTC
Jobs 1
Files 79
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

21 Oct 2026 12:42PM UTC coverage: 66.808%. Remained the same
39601816826

push

github

web-flow
feat(cli): show token permissions in command help (#7268)

Adds a PERMISSIONS section to `--help` for every command, listing the
personal access token permissions it needs.

Every command already declares the Management API operations it may
call. The help section resolves those declarations against the
permissions the API spec lists for each operation, so users can see
which token to create before running a command.

- Permissions come from a generated `operationId` to `x-fga-permissions`
/ `x-oauth-scope` table in `@supabase/api/permissions`.
- Conditions are worded against the command's own flags: a flag the
command lacks is never named, equivalent cases merge, and a permission
already shown under a broader condition is not repeated. Requirements
that depend on something other than a flag show as "May be required",
without a reason.
- `--output-format json` help carries the same section under a top-level
`permissions` field, with each group's flag conditions as data. The raw
permission declaration is no longer serialized into `doc.annotations`.
- Each permission scheme is resolved and rendered on its own, so OAuth
scopes can be added later by registering one more scheme.

Output sample:
```
$ supabase projects api-keys --help
DESCRIPTION
  List all API keys for a Supabase project.
... rest of the content ...
PERMISSIONS
  Personal access token (FGA):
    Required with --reveal:
      api_gateway_keys_read + api_gateway_keys_secret_read
    Required without --reveal:
      api_gateway_keys_read
    May be required (without --project-ref):
      projects_read
    Optional (command still runs without these):
      project_admin_read
```

```
$ supabase projects api-keys --help --output-format json
...
 "permissions": {
        "status": "mapped",
        "schemes": [
            {
                "scheme": "fga",
                "title": "Personal access token (FGA)",
                "groups": [
                    {
                        "heading":... (continued)

4110 of 6152 relevant lines covered (66.81%)

7.39 hits per line

Jobs
ID Job ID Ran Files Coverage
1 39601816826.1 21 Oct 2026 12:43PM UTC 79
66.81
GitHub Action Run
Source Files on build 39601816826
  • Tree
  • List 79
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #39601816826
  • 7e3035c6 on github
  • Prev Build on gh-readonly-queue/develop/pr-7267-3509d187e91975b9b5eabae1dad2c47cb1b4a985 (#39589085131)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc