Product Diaryby Remnant Security

SecureWatch Sheds Nearly 15,000 Leftover Build Files

Product Diary1 min readSecurity

The code history was cleared of nearly fifteen thousand leftover build files that were clogging every status check.

Every time I asked SecureWatch's repository what had changed, it answered with noise. Close to fifteen thousand files, all of them debris from compiling the software, were sitting in its history and showing up as phantom edits. I removed them from tracking on 8 October, so a status check now lists only real work. The product itself behaves exactly as before.

The exact figure was 14,861 files. They came from the Rust agent's build output, its packaged installers, and similar output folders across the apps and packages. All of it was committed before any ignore rules existed. Git keeps following whatever it has already recorded, no matter what the ignore file says afterwards, so the old rules that were meant to cover node_modules and the Rust build folders had never done anything. The disk cleanup on 7 October had already deleted the actual files. This commit simply made the repository agree.

I also replaced the narrow, path-specific ignore entries with general ones for build, dist and .next. The old entries covered only a handful of places. Nothing tracked remains under any of those three names.

The commit went in with --no-verify. The pre-commit hook calls lint-staged through pnpm, and this Mac has no pnpm, with lint-staged itself having lived in the deleted node_modules. Since the change was deletions plus one ignore file, I do not think linting had anything to check.

One mess remains: 805 tracked files from a Python virtual environment committed by mistake. Whether to remove it is a separate call.

Keep reading