fix(cli): accept URL value for --git-ref option

[Sahilshrma31]

Description

Fixes a CLI argument parsing issue where the --git-ref option was incorrectly defined as a flag instead of accepting a value.

The option is intended to take a URL (as indicated by its description), but its previous definition caused the CLI to throw an error when a value was passed. This change updates the option to correctly accept a value.

Validation

Before:

Running the CLI with a value for --git-ref fails because the option is incorrectly parsed as a boolean flag instead of accepting a value.

After:

The --git-ref option is now correctly parsed as a value option, allowing a URL to be passed without causing argument parsing errors.

Related Issues

N/A

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run node --run test and all tests passed.
• I have check code formatting with node --run format & node --run lint.
• I've covered new added functionality with unit tests if necessary.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
api-docs-tooling	Ready	Preview	Apr 13, 2026 7:25pm

[cursor]

PR Summary

Low Risk
Low risk CLI parsing fix that only changes how --git-ref is parsed by Commander, with no changes to generation logic or data handling.

Overview
Fixes generate command argument parsing by changing --git-ref from a boolean flag to a value option (--git-ref <url>), allowing callers to pass the intended URL/string without Commander throwing an “unknown option”/extra argument error.

^{Reviewed by Cursor Bugbot for commit 604ec8e. Bugbot is set up for automated code reviews on this repo. Configure here.}