chore(rebrand): rename global tool command nuke → fallout#66
Merged
Conversation
Closes #38. ## Changes - src/Fallout.GlobalTool/Fallout.GlobalTool.csproj: <ToolCommandName> flipped from `nuke` to `fallout`. Anyone installing the next published version of Fallout.GlobalTool gets `dotnet fallout` (not `dotnet nuke`). - src/Fallout.GlobalTool/Program.Complete.cs: CommandName constant flipped to "fallout". Shell completion parses `fallout <args>` now. - docs/01-getting-started/01-installation.md: post-install path-check hint references `where fallout`. - docs/architecture.md: package table + dotnet command refreshed Nuke.* → Fallout.* (the rest of the file was already updated by #54; this row was missed). ## Migration impact Existing users on `Nuke.GlobalTool` keep `dotnet nuke`; they're a different package, untouched. Existing users who already pulled `Fallout.GlobalTool` (published earlier today at 10.2.x with the legacy `nuke` ToolCommandName) will see `dotnet nuke` flip to `dotnet fallout` on next update. That's expected — Fallout.GlobalTool has been on nuget.org for hours, not days; no established muscle memory yet. Migration guide (#37) will call this out. ## Verification - dotnet build fallout.slnx -c Debug: 0 errors, 15 pre-existing warnings - dotnet test fallout.slnx: 391 passed, 7 skipped, 0 failed Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
ChrisonSimtian
added a commit
that referenced
this pull request
May 22, 2026
CLAUDE.md no longer claimed the Nuke.* → Fallout.* structural rename was pending — that landed in #54, #60, #65, #66 ages ago. Updates the rebrand-status paragraph, the src/tests layout table, the production project groupings (now including Fallout.Migrate and the vendored Fallout.VisualStudio.SolutionPersistence), the tool-wrapper paths, and fixes the CI-revival roadmap link from #7 (which is the CodeQL ticket) to #8 (the actual CI-revival tracker). README.md said releases publish to GitHub Packages — nuget.org has been the primary feed since #58. Build-status table also had three URLs hardcoded to ChrisonSimtian/nuke (the pre-rename slug). Also notes the new docs-only paths-ignore on the release workflow. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Renames the global tool's user-visible command from
dotnet nuketodotnet fallout.Closes #38.
Changes
Fallout.GlobalTool.csproj<ToolCommandName>nuke</ToolCommandName>→falloutProgram.Complete.csCommandName = "nuke"→"fallout"— shell completion parsesfallout <args>nowdocs/01-getting-started/01-installation.mdwhere nuke→where falloutdocs/architecture.mdNuke.*→Fallout.*package names +dotnet nuke→dotnet falloutMigration impact
Nuke.GlobalToolkeepdotnet nuke— different package, untouchedFallout.GlobalToolfrom nuget.org (~hours old) seedotnet nuke→dotnet fallouton next update. The migration guide ([P5] Write NUKE → Fallout migration guide #37) will call this out.Verification
dotnet build fallout.slnx -c Debug: 0 errors, 15 pre-existing warningsdotnet test fallout.slnx: 391 passed, 7 skipped, 0 failed🤖 Generated with Claude Code