[Automated] Update nbgv CLI Options

[thomhurst]

Summary

This PR contains automatically generated updates to nbgv 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:

• nbgv (3.10.91+e05abbcae4): 7 commands, tree 7a9c8d889f1ee1248bbdd066caabfaaf53477dea0c81e97ea9f405b33bda6b63
  • Baseline comparison: 7 commands at 3.10.91+e05abbcae4 -> 7 commands at 3.10.91+e05abbcae4

Verification

• Solution builds successfully

---

🤖 Generated with ModularPipelines.OptionsGenerator

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• src/ModularPipelines.NerdbankGitVersioning/Generated/Nbgv.Generation.json is excluded by !**/generated/**

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 14eef420-d956-47e4-84cd-47ced280bd4c

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.}

[github-actions]

Review: PR #4756

This PR is a single-line, bot-generated update to a generated provenance file:

--- a/src/ModularPipelines.NerdbankGitVersioning/Generated/Nbgv.Generation.json
+++ b/src/ModularPipelines.NerdbankGitVersioning/Generated/Nbgv.Generation.json
-  "generatorSourceSha256": "773b4f943140dab43ee649323893d06346286caa0635dcf177d0bfb536a63497"
+  "generatorSourceSha256": "bdf2981af64a9665cc6851ff1c5ed256989395d930ae8345ca28cd09d755e620"

Findings: None.

• No C# option classes, command logic, or tests are touched — this is purely the generatorSourceSha256 provenance field in the nbgv options-generation manifest, updated by the automated generator itself (per CLAUDE.md, this is generator output, not a hand-tweak, so the "never hand-edit generated options" rule doesn't apply here).
• Both the old and new hash values are well-formed 64-character lowercase hex strings, matching the format Assert-GeneratedOptionsFreshness.ps1 expects, so this won't break the freshness-check gate.
• The other fields (formatVersion, toolName, toolVersion, commandTreeSha256) are unchanged and the file remains valid JSON.

No architectural, design, or maintainability concerns apply to a single generated hash value — this is a clean, expected automated update.

[github-actions]

Review: PR #4756

This PR is a single-line, bot-generated update to a generated provenance file:

--- a/src/ModularPipelines.NerdbankGitVersioning/Generated/Nbgv.Generation.json
+++ b/src/ModularPipelines.NerdbankGitVersioning/Generated/Nbgv.Generation.json
-  "generatorSourceSha256": "773b4f943140dab43ee649323893d06346286caa0635dcf177d0bfb536a63497"
+  "generatorSourceSha256": "4f583590c7bc1fb5c9bd0360c7986f13acb231fe933e1989457e137aa1339444"

Findings: None.

• No C# option classes, command logic, or tests are touched — this is purely the generatorSourceSha256 provenance field in the nbgv options-generation manifest, produced by the automated generator itself (per CLAUDE.md, this is generator output, not a hand-tweak, so the 'never hand-edit generated options' rule doesn't apply here).
• Both the old and new hash values are well-formed 64-character lowercase hex strings, so this won't break the freshness-check gate.
• The other fields (formatVersion, toolName, toolVersion, commandTreeSha256) are unchanged and the file remains valid JSON.
• A previous review on an earlier commit of this PR (same kind of hash-only change) was also CLEAR; nothing outstanding carries over to this commit.

No architectural, design, or maintainability concerns apply to a single generated hash value — this is a clean, expected automated update.

[github-actions]

Review: PR #4756

This PR is a single-line, bot-generated update to a generated provenance file:

--- a/src/ModularPipelines.NerdbankGitVersioning/Generated/Nbgv.Generation.json
+++ b/src/ModularPipelines.NerdbankGitVersioning/Generated/Nbgv.Generation.json
-  "generatorSourceSha256": "773b4f943140dab43ee649323893d06346286caa0635dcf177d0bfb536a63497"
+  "generatorSourceSha256": "bccbb8765ada5091f6455448d255ca004c6b2a462256b9df4a1c67688399d5f1"

Findings: None.

• Only one file changed, and it's purely the generatorSourceSha256 provenance field in the nbgv options-generation manifest, produced by the automated generator itself (per CLAUDE.md, this is generator output, not a hand-tweak, so the 'never hand-edit generated options' rule doesn't apply here).
• Both the old and new hash values are well-formed 64-character lowercase hex strings, so this won't break the freshness-check gate.
• The other fields (formatVersion, toolName, toolVersion, commandTreeSha256) are unchanged and the file remains valid JSON.
• Previous reviews on earlier commits of this PR (same kind of hash-only change) were also CLEAR; nothing outstanding carries over to this commit.

No architectural, design, or maintainability concerns apply to a single generated hash value — this is a clean, expected automated update.

[github-actions]

test

[github-actions]

Review: PR #4756

This PR remains a single-line, bot-generated update to a generated provenance file:

```diff
--- a/src/ModularPipelines.NerdbankGitVersioning/Generated/Nbgv.Generation.json
+++ b/src/ModularPipelines.NerdbankGitVersioning/Generated/Nbgv.Generation.json

• "generatorSourceSha256": "773b4f943140dab43ee649323893d06346286caa0635dcf177d0bfb536a63497"

• "generatorSourceSha256": "b3e63ea8a8aee226da985400314ab9d242d6e9e080507f4c3bddff105af7d703"
  ```

Findings: None.

• No C# option classes, command logic, or tests are touched — only the generatorSourceSha256 provenance field in the nbgv options-generation manifest changes, produced by the automated generator itself (per CLAUDE.md, this is generator output, not a hand-tweak, so the "never hand-edit generated options" rule doesn't apply here).
• Both the old and new hash values are well-formed 64-character lowercase hex strings, so this won't break the freshness-check gate.
• The other fields (formatVersion, toolName, toolVersion, commandTreeSha256) are unchanged and the file remains valid JSON.
• Three previous reviews on earlier commits of this PR (same kind of hash-only change) were also CLEAR, and nothing outstanding carries over to this commit.

No architectural, design, or maintainability concerns apply to a single generated hash value — this is a clean, expected automated update.