Skip to content

fix(docs): correct broken flag names in recipes#451

Merged
jpoehnelt merged 1 commit intogoogleworkspace:mainfrom
anshul-garg27:fix/recipes-wrong-flag-names
Mar 13, 2026
Merged

fix(docs): correct broken flag names in recipes#451
jpoehnelt merged 1 commit intogoogleworkspace:mainfrom
anshul-garg27:fix/recipes-wrong-flag-names

Conversation

@anshul-garg27
Copy link
Contributor

Summary

Fix 18 broken flag references across registry/recipes.yaml that would cause recipe commands to fail:

Wrong flag Correct flag Count Issue
--spreadsheet-id --spreadsheet 10 Flag name mismatch
--attendees a,b --attendee a --attendee b 4 Not a comma flag — uses ArgAction::Append
--duration 30 --end <ISO8601> 4 Flag does not exist

Impact

Any AI agent or user following these recipes verbatim would get UnrecognizedArg errors. Since recipes are auto-published as SKILL.md files consumed by AI agents, this directly affects agent reliability.

Test plan

  • Verified all flag names match actual clap definitions in src/helpers/sheets.rs and src/helpers/calendar.rs
  • No remaining --spreadsheet-id, --attendees, or --duration references

Three categories of broken flags in registry/recipes.yaml:

1. --spreadsheet-id → --spreadsheet (10 occurrences)
   The actual flag in sheets.rs is --spreadsheet, not --spreadsheet-id.
   Every sheet recipe using this flag would fail.

2. --attendees → --attendee (repeated flag, 4 occurrences)
   The calendar +insert helper uses --attendee with ArgAction::Append
   for multiple attendees, not a comma-separated --attendees flag.

3. --duration → --end (4 occurrences)
   The calendar +insert helper has no --duration flag. It requires
   an explicit --end time in ISO 8601 format.
@changeset-bot
Copy link

changeset-bot bot commented Mar 12, 2026

🦋 Changeset detected

Latest commit: ff1ef1c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@googleworkspace/cli Patch

Not sure what this means? Click here to learn what changesets are.

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

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, 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 addresses critical issues in the registry/recipes.yaml file by correcting several broken command-line flag references. These fixes ensure that AI agents and users can execute the provided recipes without encountering UnrecognizedArg errors, thereby improving the reliability of automated processes and user guidance.

Highlights

  • Spreadsheet ID Flag Correction: Changed --spreadsheet-id to --spreadsheet in 10 instances within registry/recipes.yaml to align with the correct flag name for Google Sheets commands.
  • Calendar Attendees Flag Update: Modified --attendees a,b to use multiple --attendee flags (e.g., --attendee a --attendee b) in 4 instances, reflecting the ArgAction::Append behavior for calendar event creation.
  • Calendar Event Duration Flag Fix: Replaced the non-existent --duration flag with the correct --end <ISO8601> flag for calendar event creation in 4 instances, also updating the start time format to ISO8601.
Changelog
  • .changeset/fix-recipe-flag-names.md
    • Added a new changeset file documenting the fix for recipe flag names.
  • registry/recipes.yaml
    • Updated --spreadsheet-id to --spreadsheet in various gws sheets commands.
    • Corrected --attendees flag usage to --attendee for multiple attendees in gws calendar +insert commands.
    • Replaced the --duration flag with --end and adjusted date formats in gws calendar +insert commands.
Activity
  • No human activity (comments, reviews, or progress updates) has been recorded for this pull request yet.
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 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.

Copy link
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 correctly fixes several broken flag names in the CLI recipes, which is a crucial correction for usability. The changes properly replace --spreadsheet-id with --spreadsheet, handle --attendees as an appendable flag, and replace the non-existent --duration flag with --end. My review identifies a potential correctness issue in the updated calendar event creation commands. The timestamps for start and end times are missing timezone information, which can lead to ambiguity and incorrect event creation. I've suggested adding UTC timezone specifiers for consistency and to ensure events are created at the correct time.

@jpoehnelt jpoehnelt merged commit 8fce003 into googleworkspace:main Mar 13, 2026
29 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants