The docspress npm executable currently provides one command: token.
Top-level help
npx docspress@0.2.0 --helpDocspress CLI
Usage:
docspress token --client-id CLIENT_ID --client-secret CLIENT_SECRET --site fkadev.blog --repo f/docspress-demo
Commands:
token Create and optionally store a WordPress.com OAuth token.
Unknown commands exit with an error. The CLI does not publish documentation from a local command; synchronization runs through the GitHub Action.
Token options
| Option | Required | Purpose |
|---|---|---|
--client-id | yes | WordPress.com application client ID. |
--client-secret | yes | WordPress.com application client secret. Keep it outside chat and shell history. |
--site | no | Site domain or ID supplied to the authorization screen. |
--scope | no | OAuth scope; defaults to global. |
--redirect-uri | no | Local HTTP callback; defaults to http://localhost:8787/callback. |
--repo | required with --set-secret | GitHub repository in OWNER/REPO form. |
--set-secret | no | Stores the access token as WP_ACCESS_TOKEN through GitHub CLI instead of printing it. |
The redirect must use http and the hostname must be localhost or 127.0.0.1. The helper generates and validates OAuth state before exchanging the authorization code.
See Authenticate WordPress for the recommended invocation.