chore: delete legacy IDE files + move references → docs/cli-tools#71
Merged
Merged
Conversation
Cleanup sweep — nothing in the codebase relied on these.
## Deleted (5 IDE files)
Matt-era ReSharper/EditorConfig files left over after the takeover:
- build/.editorconfig
- build/_build.csproj.DotSettings
- src/Fallout.Components/Fallout.Components.csproj.DotSettings
- src/Fallout.GlobalTool/templates/.editorconfig (template)
- src/Fallout.GlobalTool/templates/_build.csproj.DotSettings (template)
CLAUDE.md already had a "don't reintroduce these" guard ("relying on
dotnet format defaults and review") — the file just hadn't been
truthful yet. Now it is.
`Program.Setup.cs` updated to stop emitting the two template files into
fresh consumer projects from `dotnet fallout :setup`.
## Moved (46 reference files)
`build/references/*.txt` → `docs/cli-tools/*.txt`.
Plain-text snapshots of upstream CLI documentation, used as a drift-
detection aid by the `References` build target. Doesn't belong under
`build/` (it's not a build input) and `docs/cli-tools/` is the right
home — opens the door to per-tool tutorial markdown landing alongside.
- build/Build.CodeGeneration.cs: ReferencesDirectory points at the new
location.
- docs/cli-tools/README.md: explains what the .ref.NNN.txt files are,
how to regenerate, and what's intended vs out of scope.
## Verification
- dotnet build fallout.slnx: 0 errors, 15 pre-existing warnings
- dotnet test fallout.slnx: 408 passed, 7 skipped, 0 failed
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
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
Cleanup sweep. Nothing in the codebase relied on these files.
Deleted
Five Matt-era IDE/ReSharper/EditorConfig files left over after the takeover:
build/.editorconfigbuild/_build.csproj.DotSettingssrc/Fallout.Components/Fallout.Components.csproj.DotSettingssrc/Fallout.GlobalTool/templates/.editorconfigsrc/Fallout.GlobalTool/templates/_build.csproj.DotSettingsCLAUDE.mdalready had a "don't reintroduce these" guard (relying ondotnet formatdefaults and review) — the file just hadn't been truthful yet. Now it is.Program.Setup.csupdated to stop emitting the two template files into fresh consumer projects fromdotnet fallout :setup.Moved
46 reference files from
build/references/→docs/cli-tools/.Plain-text snapshots of upstream CLI documentation, used as a drift-detection aid by the
Referencesbuild target. Doesn't belong underbuild/(it's not a build input).docs/cli-tools/is the right home — opens the door to per-tool tutorial markdown landing alongside.build/Build.CodeGeneration.csReferencesDirectorypoints at the new location.docs/cli-tools/README.md(new).ref.NNN.txtfiles are, how to regenerate, and intended vs out-of-scope use.Verification
dotnet build fallout.slnx -c Debug: 0 errors, 15 pre-existing warningsdotnet test fallout.slnx: 408 passed, 7 skipped, 0 failed🤖 Generated with Claude Code