Repository navigation
chore: remove .vscode directory - #418
Merged
Merged
Conversation
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
Remove the tracked
.vscode/directory and its three files:.vscode/c_cpp_properties.old.json.vscode/launch.json.vscode/settings-example.jsonThis is a repository-cleanup change only; it does not touch build logic, runtime code, or target configuration.
Motivation
The tracked VS Code files are editor-specific and have become stale:
launch.jsonpoints attarget/aarch64/debug/hvisor, which no longer matches the current build layout.c_cpp_properties.old.jsonhardcodes an old cross-GCC path and is explicitly marked as an old configuration.settings-example.jsonhardcodes a target triple and has to be updated every time the target changes (for example, the AArch64 softfloat migration).VS Code settings are also personal/environment-specific. The generated
.vscode/settings.jsonis already ignored by Git and is recreated bymake vscode/host_config.sh, so keeping an example file in the repository only adds maintenance cost.Verification
git ls-files .vscodereturns no tracked files.make ARCH=aarch64 BOARD=qemu-gicv3 defconfigsucceeds.git status --shortis clean after the change.No runtime or QEMU test is needed for an editor-configuration-only removal.
Risks and Limitations
rust-analyzer.cargo.targetlocally.make vscode/tools/kconfig/host_config.sh vscodecan still create an ignored local.vscode/settings.json; this PR removes tracked files only, not the local-generation behavior.