TatuEngine packed its bags — and the repo got lighter
What git hides (without meaning to)
Every personal repo accumulates junk: build/ with binaries from one run, intermediate artifacts, folders generated by a tool that shouldn’t be versioned. In TatuEngine, that was build_py/ — the result of local builds leaking into version control.
A double problem: (1) it bloats the repo with bytes that don’t tell the real story, and (2) for a project carrying sensitive code underneath, every extra file is one less chance of controlled privacy.
The cleanup
Two moves:
- Remove
build_py/from versioning — build artifacts don’t belong in history. The source and build scripts are enough; the build product regenerates. - Auto-sync running clean — the repo keeps its routine auto-sync (end-of-day + weekly), but now only pushes real changes, without dragging generated artifacts along.
Why it matters (especially here)
In TatuEngine, “build in public” is a thin line: show the journey, don’t hand over the recipe. Versioning hygiene is part of that — it guarantees that what’s versioned is what makes sense to show, and that build data and internal drafts don’t scramble the narrative or the security.
Lesson
Version control is not a backup of your disk — it’s the public statement of what that code is. If the build folder shouldn’t be history, it doesn’t stay. Keep the repo as a clean showcase: code, scripts, decisions — and generate the rest at runtime.