Skip to content

docs(cli): include generate help#17

Merged
roderik merged 1 commit intomainfrom
docs/cli-generate-help
Sep 17, 2025
Merged

docs(cli): include generate help#17
roderik merged 1 commit intomainfrom
docs/cli-generate-help

Conversation

@roderik
Copy link
Copy Markdown
Member

@roderik roderik commented Sep 17, 2025

Summary by Sourcery

Include the generate command help in the README and update the docs generation script to append its output.

Build:

  • Extend the docs:cli npm script to run bun src/index.ts generate --help and include its output in the generated README

Documentation:

  • Add Usage and Options sections for the network-bootstrapper generate command to the CLI documentation in README.md

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Summary of Changes

Hello @roderik, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly improves the project's command-line interface documentation by embedding the detailed help for the generate command directly into the README.md. This change makes it easier for users to understand and utilize the generate command's various options without needing to execute the command itself. Furthermore, the process of updating this documentation has been automated, ensuring consistency and reducing manual effort.

Highlights

  • Documentation Update: The README.md file now includes comprehensive help documentation for the generate CLI command, detailing its usage and all available options with their descriptions and default values.
  • Automated CLI Documentation Generation: The docs:cli script in package.json has been updated to automatically append the help output for the generate subcommand to the README.md file, ensuring the documentation remains current.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@github-actions github-actions Bot added the qa:running QA workflow is currently running label Sep 17, 2025
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Sep 17, 2025

To view in Slack, search for: 1758128715.298869

@roderik roderik merged commit 862012b into main Sep 17, 2025
8 of 9 checks passed
@roderik roderik deleted the docs/cli-generate-help branch September 17, 2025 17:05
Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

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

Hey there - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@github-actions github-actions Bot added status:merged Pull request has been merged status:ready-for-review Pull request is ready for review and removed status:merged Pull request has been merged labels Sep 17, 2025
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the documentation generation script to include the help output for the generate subcommand in the README.md. While this is a good addition, the implementation can be improved. The script concatenates two separate help outputs into a single code block, which harms readability. I've suggested an update to the script in package.json to create separate, headed code blocks for each command's help output, which will improve the structure and clarity of the documentation.

Comment thread package.json
"helm": "helm upgrade --install network ./charts/network -n network --create-namespace --timeout 15m",
"docs:helm": "helm-docs --chart-search-root=. --skip-version-footer",
"docs:cli": "cat README.tpl > README.md && echo '\n```' >> README.md && bun src/index.ts --help >> README.md && echo '```' >> README.md",
"docs:cli": "cat README.tpl > README.md && printf '\\n```\\n' >> README.md && bun src/index.ts --help >> README.md && printf '\\n\\n' >> README.md && bun src/index.ts generate --help >> README.md && printf '\\n```\\n' >> README.md",
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.

medium

The docs:cli script is becoming long and hard to read. More importantly, it concatenates the help output of two different commands into a single markdown code block in README.md. This makes the documentation less clear and structured.

For better readability and semantic structure in the generated README.md, I suggest splitting the output into two separate, headed code blocks. This also makes the script's intent clearer.

As this script grows, you might also consider moving it to a separate shell script file (e.g., in a scripts/ directory) and calling it from here. This would significantly improve maintainability.

    "docs:cli": "cat README.tpl > README.md && printf '\\n### Main command\\n\\n\`\`\`text\\n' >> README.md && bun src/index.ts --help >> README.md && printf '\\n\`\`\`\\n\\n### \`generate\` command\\n\\n\`\`\`text\\n' >> README.md && bun src/index.ts generate --help >> README.md && printf '\\n\`\`\`\\n' >> README.md",

@github-actions github-actions Bot added qa:success QA workflow passed successfully docs Documentation changes and removed qa:running QA workflow is currently running labels Sep 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Documentation changes qa:success QA workflow passed successfully status:ready-for-review Pull request is ready for review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant