Knowledge Base v3.3: WP-CLI commands, GitHub import tools and more
Managing a knowledge base from the WordPress dashboard works well until you need to run the same checks and updates across several sites. Knowledge Base Pro v3.3 adds WP-CLI commands for GitHub documentation sync and common maintenance, plus updated Abilities API tools for guided imports. I’ve also fixed two issues that could expose or overwrite GitHub credentials and leave a renamed article out of date.
WP-CLI commands for Knowledge Base Pro
The new wp wzkb commands put Knowledge Base searches, status checks and maintenance in the same shell where you already run WordPress updates. They are available when Knowledge Base Pro and WP-CLI are active.
Use wp wzkb status to see the counts for published and draft articles, sections and products. wp wzkb search <query> searches published Knowledge Base articles and accepts the standard output formats supported by WP-CLI, including JSON and CSV. For example:
Other commands cover cache clearing, settings and article ratings. Settings can be read with wp wzkb settings get <key> or exported with wp wzkb settings export. Sensitive values are excluded from exports and cannot be read with the settings command. Cache clearing asks for confirmation unless you pass --yes, and supports --dry-run where applicable.
If you use Ask the Docs, wp wzkb ai can check its status, ask a question, list or clear recorded content-gap questions, and clear cached answers. AI requests use the provider and usage limits already configured for the site.
GitHub documentation sync from the command line
The GitHub commands use the repository mappings and credentials already saved in Knowledge Base settings. You don’t need to put a personal access token in a shell command.
Check a mapping with wp wzkb github status, review source differences with wp wzkb github diff, or preview an import before it changes any articles:
When the preview looks right, run the import with --yes to confirm it without an interactive prompt. The import uses each mapping’s configured product, article status and duplicate-handling rules. An export can push linked articles back to GitHub, but only when the mapping has push-back enabled and the remote source still matches the saved sync baseline. Conflicts stop the export instead of overwriting a changed remote file.
The new commands are useful for scheduled maintenance and repeatable deployment workflows. Start with a dry run when an import or export will change content, then review the reported paths and actions before confirming it. See the Knowledge Base WP-CLI commands guide for the full command list and options. For general command-line usage, see the WP-CLI command reference.
GitHub import abilities for connected tools
Knowledge Base Pro also adds three Abilities API tools for GitHub imports: knowledgebase/list-github-mappings, knowledgebase/preview-github-import and knowledgebase/import-github-articles. An agent or integration can list enabled import sources without receiving their credentials, preview selected files, then import only the requested mapping or files.
The preview reports the action each file would take, such as creating, updating, skipping or excluding an article. It follows the same parsing and duplicate-handling rules as an import. The import ability returns per-file results and does not expose GitHub tokens.
The free plugin continues to provide its read-only article search and section-discovery abilities. For the input and output details, see the Knowledge Base Abilities API reference.
Other changes in this release
The Product Migration wizard is deprecated and will be removed in v3.4.0. It remains available in v3.3.0, so sites using it can complete their migrations before upgrading to v3.4.0.
A GitHub file rename could leave its Knowledge Base article showing older content if the first attempt to fetch the renamed file failed. Knowledge Base Pro now tracks the old source path until it successfully imports the renamed file, allowing a later attempt to finish the update.
Settings exports no longer include the saved GitHub token for each repository mapping. Importing a settings file also preserves the token already saved for each matching mapping, so a file from another site can’t replace those credentials.
Upgrade notes
Knowledge Base v3.3 requires WordPress 6.9 or later and PHP 7.4 or later. This release has no migration step. The WP-CLI commands require WP-CLI to be installed; the GitHub sync commands also require an enabled repository mapping. Ask the Docs commands use the provider and limits you have already configured.
If you use the Product Migration wizard, finish that work before upgrading to v3.4.0, when the wizard is scheduled for removal.