Skip to content

docs: use supabase docs as source of truth#319

Merged
raulb merged 2 commits into
mainfrom
raulb/minor-readme-update
Jul 6, 2026
Merged

docs: use supabase docs as source of truth#319
raulb merged 2 commits into
mainfrom
raulb/minor-readme-update

Conversation

@raulb

@raulb raulb commented Jul 6, 2026

Copy link
Copy Markdown
Member

What kind of change does this PR introduce?

  • Docs update.
  • Updates mgmt-api types
mcp-server-supabase/ on raulb/minor-readme-update
› pnpm generate:management-api-types

> @supabase/mcp-server-supabase@0.8.2 generate:management-api-types /Users/rb/code/supabase/mcp/packages/mcp-server-supabase
> openapi-typescript https://api.supabase.com/api/v1-json -o ./src/management-api/types.ts

✨ openapi-typescript 7.9.1
🚀 https://api.supabase.com/api/v1-json → ./src/management-api/types.ts [889.4ms]

What is the current behavior?

This content exists in both the repo's readme and public docs.

What is the new behavior?

Leave a link for reference.

Linked content that exists in the public docs.
@raulb raulb self-assigned this Jul 6, 2026
@coveralls

coveralls commented Jul 6, 2026

Copy link
Copy Markdown

Coverage Report for CI Build 28798656122

Warning

No base build found for commit 84f1c60 on main.
Coverage changes can't be calculated without a base build.
If a base build is processing, this comment will update automatically when it completes.

Coverage: 96.243%

Details

  • Patch coverage: No coverable lines changed in this PR.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

Requires a base build to compare against. How to fix this →


Coverage Stats

Coverage Status
Relevant Lines: 2820
Covered Lines: 2735
Line Coverage: 96.99%
Relevant Branches: 347
Covered Branches: 313
Branch Coverage: 90.2%
Branches in Coverage %: Yes
Coverage Strength: 41.36 hits per line

💛 - Coveralls

@raulb raulb mentioned this pull request Jul 6, 2026
@raulb raulb merged commit c3b97f6 into main Jul 6, 2026
5 checks passed
raulb added a commit that referenced this pull request Jul 6, 2026
## What kind of change does this PR introduce?

Make sure every PR need to be reviewed by the AI team.

Working on #319 I realized that this
is not the default behavior.

## What is the current behavior?

We're not notified by open PRs, and anybody with right permissions could
merge those PRs.

## What is the new behavior?

AI team is notified, and someone from this team needs to approve it
before merging.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants