Repository navigation
Conversation
Contributor
Author
|
generate-docs.mp4 |
Prints a command's usage line, subcommands, and options as markdown in the format docs.livekit.io's CLI reference uses (e.g. `lk generate-docs agent deploy`). docs.livekit.io regenerates its CLI reference from this on every release.
Ports the CLI reference's descriptions for the agent, simulate, debugger, private-link, cloud auth, project, and docs commands into their flag and subcommand help, and gives every value flag a placeholder, so the generated reference reads like the current hand-written one.
u9g
force-pushed
the
jason/generate-docs
branch
from
October 12, 2026 20:32
48c59b8 to
3c9fe72
Compare
bcherry
approved these changes
Oct 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
docs.livekit.io's CLI reference is hand-written, so every flag or subcommand change in
lkhas to be re-documented separately and drifts almost immediately. This makes the CLI's own help text the source of truth for that reference.lk generate-docs <command path>(hidden) prints a command's usage line, its subcommands, and its options as markdown, in the format the docs.livekit.io CLI reference already uses:It reads the same flag data
--helpprints: the first backticked word in a flag's usage is its value placeholder, defaults come from the flag's value, and hidden commands, hidden flags, and the--helpflag are left out. The heading, description, and examples around it stay hand-written on the docs page.Help text aligned with the docs: the CLI reference's current descriptions for the agent, simulate, debugger, private-link, cloud auth, project, and docs commands are ported into their help text, and every value flag gets a placeholder (
--region REGIONrather than--region string). Switching the docs to generated output then changes little on the page, and--helpgets the docs' wording.cloud auth --revokegets the usage text it was missing.notify-docs.yamlruns when a release is published (prereleases are skipped). It dispatcheslivekit-cli-releasedwith the tag to livekit/internal-actions, which forwards it to livekit/web. That workflow downloads the release'slk, regenerates the reference withlk generate-docs, and opens a docs PR. It uses the existing org secretSYNC_DISPATCH_TOKEN, the same relay agent-skills uses, so no credential that writes to livekit/web lives in this public repo.To change wording on docs.livekit.io, edit the command's help text here; the next published release updates the docs.
Related:
How to verify