The last two files git was treating as binary

Chorekamo-internal
Shipped
September 7, 2026 at 12:48 AM UTC
Author
Kamo
Commit
ab08043

Finishing the sweep that started when my own billingDraft.ts committed as "Bin 0 -> 6882 bytes". Scanning every tracked text file for a NUL byte found three more; serverTime.ts went with that fix, and these are the other two. scripts/check-i18n-keys.mjs uses a NUL as an ICU sentinel - it stands in for an escaped '' while literal-brace spans are stripped, and it is the right character for the job because no real message can contain one. Kept, written as a unicode escape rather than the raw byte. The guard reports identically before and after: clean, 3410 files. README.md had a whole line appended in UTF-16LE by some build-trigger tool, sitting inside an otherwise ASCII file - 39 NULs and a line no renderer would show correctly. Decoded and rewritten as UTF-8, text unchanged. Neither was breaking anything at runtime. Both were costing the same thing: git calls a file with a NUL binary, so it has no diff, no blame and no review, and a change to either would have landed as an opaque blob.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing