fix: include service name in help usage

[zerone0x]

Summary

Fixes #839

Ensure generated service help renders the full invocation path (for example, gws sheets spreadsheets) instead of dropping the service name after argv is filtered for Clap.

Changes

• Set the service-specific Clap command tree bin_name to gws <service> before parsing filtered arguments.
• Keeps command parsing unchanged while correcting help/usage output for nested resources.

Test Plan

• cargo fmt -- --check
• cargo test -q (blocked in this environment: linker cc is not installed, so Rust build scripts for dependencies fail before tests compile)

[changeset-bot]

⚠️ No Changeset found

Latest commit: c5ef28e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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 addresses an issue where the help usage output for nested service commands was missing the service name. By explicitly setting the bin_name for the Clap command tree, the CLI now correctly renders the full invocation path in help documentation, improving the user experience for command discovery.

Highlights

• Help command usage: Updated the CLI command tree to include the service name in the bin_name, ensuring that help text displays the correct full invocation path.

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 the 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 counterproductive. 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.

Footnotes

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

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[gemini-code-assist]

Code Review

This pull request updates the CLI initialization in crates/google-workspace-cli/src/main.rs to dynamically set the binary name using .bin_name(format!("gws {first_arg}")). This ensures that nested help and usage text render correctly with the full binary invocation. There are no review comments, and I have no feedback to provide.