[Automated] Update gh CLI Options

[thomhurst]

Summary

This PR contains automatically generated updates to gh CLI options classes.

The generator scraped the latest CLI help output from the installed tool.

Changes

• Updated options classes to reflect latest CLI documentation
• Added new commands if any were detected
• Updated option types and descriptions

Assembly-wide public API impact

No active public API changes were detected in this assembly.

Command coverage

Command coverage report:

• gh (gh version 2.100.0 (2026-09-03) https://github.com/cli/cli/releases/tag/v2.100.0): 221 commands, tree 3777cffcf304b41a18323a005d1f5bfd5dd24121249da59c9d985e6b8132d552
  • Baseline comparison: 221 commands at gh version 2.100.0 (2026-09-03) https://github.com/cli/cli/releases/tag/v2.100.0 -> 221 commands at gh version 2.100.0 (2026-09-03) https://github.com/cli/cli/releases/tag/v2.100.0

Verification

• Solution builds successfully

---

🤖 Generated with ModularPipelines.OptionsGenerator

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review (1)

• main

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: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 3903731e-4434-4be4-97e3-1af94fe61080

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

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-14T06:05:36.045480Z	a8ae7e2	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[greptile-apps]

Greptile Summary

This PR updates only the gh generated-options provenance fingerprint. The tool version and command-tree fingerprint remain unchanged, and the new generator-source fingerprint correctly matches the PR base.

• Updates generatorSourceSha256 in the gh generation manifest.
• Does not change generated option classes or runtime behavior.

Confidence Score: 5/5

The PR appears safe to merge because the sole metadata update is internally consistent with the generator freshness check.

No actionable failures remain; the replacement fingerprint matches the deterministic hash of the configured generator-source paths at the PR base.

Important Files Changed

Filename	Overview
src/ModularPipelines.GitHub/Generated/Gh.Generation.json	Updates the generator-source provenance hash to the value expected for the current base generator inputs.

_{Reviews (1): Last reviewed commit: "chore: Update gh CLI options" | Re-trigger Greptile}

[github-actions]

Code review

This PR is fully automated: the only change is the generatorSourceSha256 provenance value in src/ModularPipelines.GitHub/Generated/Gh.Generation.json (0e7b8148... → 50a6ccfc...). No generated option classes or command coverage changed (221 commands before and after, same commandTreeSha256).

I verified the update is expected rather than spurious: generatorSourceSha256 is a SHA-256 over the git object IDs of a fixed list of generator-source paths (scripts/GeneratedOptionsProvenance.ps1), and the most recent commit on main (c66bb4e, #4547) rewrote .github/workflows/generate-cli-options.yml, which is one of the hashed inputs. That alone is enough to change the fingerprint for every tool's provenance file, so a regeneration PR for gh updating just this field is the correct, minimal output — hand-editing it or preserving the old value would violate the repo's "current tool output is authoritative" rule for generated options.

No issues found. Checked for bugs and CLAUDE.md compliance.