Skip to content

Conversation

@JEETDESAI25
Copy link
Contributor

What kind of change does this PR introduce?

Documentation improvement

What is the current behavior?

Closes #218

The organization_id parameter lacks clarity, users don't know it refers to the organization slug found in the dashboard URL. Additionally, import documentation is missing for all resources (project, settings, branch).

What is the new behavior?

  • Updated organization_id schema description to specify it's the organization slug
  • Added custom templates with Import sections for all three resources
  • Added inline comment in README.md example

Additional context

Regenerated docs via go generate ./.... Minor merge conflict possible with PR #255 in project_resource.go (both changes should be kept).

@JEETDESAI25 JEETDESAI25 requested a review from a team as a code owner November 26, 2025 01:35
@JEETDESAI25 JEETDESAI25 force-pushed the fix/issue-218-doc-org-id-import branch from 551e1b7 to 9c162f2 Compare November 26, 2025 01:46
Copy link
Collaborator

@savme savme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for updating the docs, @JEETDESAI25! I think we can use a simpler approach for the import syntax descriptions

@JEETDESAI25 JEETDESAI25 force-pushed the fix/issue-218-doc-org-id-import branch from 9c162f2 to cf27730 Compare December 1, 2025 06:13
@savme savme enabled auto-merge (squash) December 2, 2025 06:44
@savme savme merged commit dfcfe6d into supabase:main Dec 2, 2025
6 checks passed
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.

Doc - organiaztion_id is for organization slug / missing import

2 participants