.gitattributes

# The DevTools UI bundle, embedded as base64 by `bun run build:ui`.
# `linguist-generated` keeps it out of the language statistics and
# collapses it by default in GitHub's review view; the file is committed
# on purpose (see scripts/build-devtools-ui.mjs) so typecheck, tests and
# smoke runs work straight from a fresh clone.
#
# It is deliberately NOT `-diff`.  That token made git and GitHub report
# the module as binary ("Bin 48579 -> 48898 bytes") — which hid the only
# thing anyone can actually check about the payload.  `bun run check:ui`
# proves the committed `source-hash` matches the sources it claims; it
# says nothing about whether the base64 beside it is what those sources
# compiled to (the bytes are not reproducible across OS and Bun release,
# which is why it hashes sources instead).  So a payload edited without
# touching `devtools-ui/**` is caught in review or not at all, and with
# a textual diff it is easy to catch: `gzipBase64` / `size` / `etag` move
# while `source-hash` and the UI sources stay put.  A regenerate is 7
# changed lines, only 2 of them multi-KB, because unchanged chunks keep
# their content-hashed names — the cost is `git show` noise locally, not
# review load, and `git diff --stat`, a pathspec exclude or a per-clone
# `.git/info/attributes` handles that without hiding it from everybody.
#
# `eol=lf` matters as much as the rest: the build writes LF, so without
# it a CRLF checkout reports the file as modified after every build —
# permanent noise in `git status` for every Windows contributor.
src/devtools/generated/UiAssets.ts linguist-generated diff text eol=lf

# The DevTools UI sources are bundled into the generated module above
# and fingerprinted by its `source-hash`, so their bytes must not depend
# on a checkout's line-ending conversion — otherwise the same commit
# hashes differently on Windows than on Linux and the freshness check
# fails for half the contributors.  The build normalises what it reads
# as well; this is the other half of that pair.
devtools-ui/** text eol=lf

# The JVM arms' committed build-tool launcher (#1229).  Both of these are
# parsed, not just executed, so a checkout that rewrites their line endings
# breaks them in ways that read as anything but a line-ending problem.
#
# `.mill-version` is read as a string and spliced into a download URL: a
# trailing CR asks Maven Central for a version that does not exist.  The POSIX
# launcher is worse — `#!/usr/bin/env sh\r` is not an interpreter, so the file
# fails to start at all, and only on the platforms where it is the only entry
# point.  Neither is hypothetical here: `core.autocrlf=true` is the Windows
# default, and it rewrites both on checkout.
#
# The Windows launcher keeps CRLF on purpose — it is a batch file.
benchmarks/comparison/**/.mill-version text eol=lf
benchmarks/comparison/**/mill          text eol=lf
benchmarks/comparison/**/mill.bat      text eol=crlf
graphify-out/graph.json merge=graphify