Removed the stray build artifacts committed with the RISC-V64 port fix - #706
Merged
fdesbiens merged 1 commit intoSep 9, 2026
Merged
Conversation
A local CMake build tree was staged by mistake alongside the RISC-V64 spec compliance work in eclipse-threadx#698, putting nine generated files on dev, including a compiled kernel.elf, build.ninja, the Ninja dependency logs and a QEMU run log. None of it belongs in the repository. The root .gitignore listed build directories by name rather than by pattern, so build/, build_qemu/, build_m7/ and the build_r52 variants were covered but a differently named tree was not. Those entries are replaced with a single build*/ pattern, which covers every existing name and any future one. No tracked file matches the new pattern. The artifacts remain reachable in history; only the working tree is corrected, since rewriting a shared branch is the greater harm. Assisted-by: Claude Code (Opus 5) <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.
A local CMake build tree was staged by mistake alongside the RISC-V64 spec compliance work in #698, so nine generated files landed on
dev:build-rv64/build.ninjabuild-rv64/ports/risc-v64/gnu/example_build/qemu_virt/kernel.elfbuild-rv64/.ninja_depsbuild-rv64/.ninja_logbuild-rv64/custom_inc/tx_user.hbuild-rv64/ports/risc-v64/gnu/example_build/qemu_virt/qemu-riscv64.logbuild-rv64/ports/risc-v64/gnu/example_build/qemu_virt/test_cmds.gdbbuild-rv64/CPackSourceConfig.cmakebuild-rv64/CPackConfig.cmakeNone of it belongs in the repository, and none of it is part of the RISC-V64 fix itself — that change is correct and stays as merged.
Why the ignore rules did not catch it
The root
.gitignorelisted build directories by name rather than by pattern:Every one of those is a name someone happened to use. A tree configured under any other name was staged normally. Those eight entries are replaced with a single
build*/, which covers all of them and anything future. I confirmed no tracked file matches the new pattern:example_build/directories are unaffected, since the pattern anchors on names beginning withbuild.On history
The blobs stay reachable in
dev's history. Only the working tree is corrected — rewriting a shared branch that contributors have already pulled is the greater harm for 830 KB of dead objects.