Skip to content

fix(docs): align CLI help text with commands reference for check-docs parity#2332

Closed
gaveezy wants to merge 1 commit into
NVIDIA:mainfrom
gaveezy:fix/nightly-e2e-cli-docs-parity-04757ed
Closed

fix(docs): align CLI help text with commands reference for check-docs parity#2332
gaveezy wants to merge 1 commit into
NVIDIA:mainfrom
gaveezy:fix/nightly-e2e-cli-docs-parity-04757ed

Conversation

@gaveezy

@gaveezy gaveezy commented Apr 23, 2026

Copy link
Copy Markdown

Summary

The check-docs CI step (cloud-experimental-e2e) fails because the
CLI --help output and docs/reference/commands.md headings are out
of sync.

Root causes (all three fixed here):

  1. Single-space description separators in help()
    channels remove, policy-remove, and credentials reset used
    a single space before their description text. The check-docs.sh
    normalizer expects 2+ spaces as the delimiter, so description text
    leaked into the normalized command signature, producing phantom
    mismatches. Widened to 2 spaces.

  2. Inconsistent trailing-arg stripping — the help-side normalizer
    strips trailing <arg> and [optional] placeholders, but the
    docs-side normalizer did not. Commands like
    nemoclaw <name> channels add <channel> (docs) normalized
    differently from nemoclaw <name> channels add (help). Added the
    same stripping to the docs perl extraction script.

  3. Missing ### headings — four commands present in --help had
    no level-3 heading in docs/reference/commands.md:
    onboard --from, setup, start, stop. Added headings for
    each (the latter three are deprecated aliases).

Note: The same cloud-experimental-e2e job also reports a Landlock
/sandbox writability failure in its step 3 (04-landlock-readonly).
That is an intermittent infrastructure-level issue unrelated to these
documentation changes and is tracked separately.

Test plan

  • Re-run cloud-experimental-e2e on this branch — the
    check-docs.sh step should pass
  • Verify nemoclaw --help output still renders correctly
  • Confirm no other nightly-e2e jobs regress

Signed-off-by: Hai Nguyen haingu@nvidia.com

🤖 Generated with Claude Code

Fixes #2333

… parity

Three issues caused the check-docs CLI parity check to fail:

1. Three help() lines in src/nemoclaw.ts used single-space separation
   between the command signature and its description, so the check-docs
   normalizer included description text in the normalized output. Fixed
   by widening to 2+ spaces (channels remove, policy-remove, credentials
   reset).

2. The docs-side normalizer in check-docs.sh did not strip trailing
   <arg> and [optional] placeholders the way the help-side normalizer
   does, producing false mismatches for commands like channels add
   <channel>. Added the same stripping to the docs extraction perl
   script.

3. Four commands present in --help had no ### heading in
   docs/reference/commands.md: onboard --from, setup, start, stop.
   Added headings for each (the latter three are deprecated aliases).

Signed-off-by: Hai Nguyen <haingu@nvidia.com>
@copy-pr-bot

copy-pr-bot Bot commented Apr 23, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@coderabbitai

coderabbitai Bot commented Apr 23, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 4aff9223-6440-4371-a1cc-e609b4d013b7

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@wscurran

Copy link
Copy Markdown
Contributor

✨ Thanks for submitting this issue that identifies a bug with the CLI help text and proposes a fix. Let us know when the draft is completed.


Related open issues:

@gaveezy gaveezy closed this Apr 24, 2026
@cv cv added v0.0.25 and removed v0.0.25 labels Apr 24, 2026
@wscurran wscurran added area: ci CI workflows, checks, release automation, or GitHub Actions chore Build, CI, dependency, or tooling maintenance area: docs Documentation, examples, guides, or docs build and removed CI/CD labels Jun 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: ci CI workflows, checks, release automation, or GitHub Actions area: docs Documentation, examples, guides, or docs build chore Build, CI, dependency, or tooling maintenance

Projects

None yet

Development

Successfully merging this pull request may close these issues.

nightly-e2e: check-docs CLI/docs parity mismatch (cloud-experimental-e2e step 4)

3 participants