Skip to content

docs(extensions): fix private catalog FAQ command - #4373

Open
WOLIKIMCHENG wants to merge 1 commit into
github:mainfrom
WOLIKIMCHENG:docs/extension-catalog-add-command
Open

docs(extensions): fix private catalog FAQ command#4373
WOLIKIMCHENG wants to merge 1 commit into
github:mainfrom
WOLIKIMCHENG:docs/extension-catalog-add-command

Conversation

@WOLIKIMCHENG

Copy link
Copy Markdown
Contributor

Summary

  • Replace the obsolete private-catalog FAQ command with specify extension catalog add.
  • Document the required project context and catalog name.
  • Remove the stale Phase 4 implementation note while retaining the safe discovery-only default.

Validation

  • .venv/bin/specify extension catalog add --help
  • git diff --check origin/main
  • Verified command and default-policy parity against the current implementation and extension references.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

馃煝 Approval recommended

The documentation matches the implemented command syntax and discovery-only default.

Pull request overview

Updates the private-extension FAQ to match the current project-scoped catalog CLI.

Changes:

  • Replaces the obsolete command.
  • Documents the required catalog name and project context.
  • Removes the outdated implementation note.
File summaries
File Description
extensions/EXTENSION-PUBLISHING-GUIDE.md Corrects private catalog setup guidance.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Balanced

馃挕 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

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