Gitattributes - End-of-Line Normalisation Rules
The attribute file that decides what happens to line endings on checkout: `text=auto` as the default, explicit `eol=lf` and `eol=crlf` overrides, the `binary` macro that expands to `-text -diff`, and one `-text` entry that is still given a textconv driver. This is the file whose absence causes the CRLF twins elsewhere in this category.
# Let git decide what is text, and store it with LF in the repository
* text=auto
# Always LF in the working tree, whatever the platform
*.sh text eol=lf
*.py text eol=lf
# Always CRLF in the working tree — these break otherwise
*.bat text eol=crlf
*.sln text eol=crlf
# Never touch these: no normalisation, no diffing as text
*.png binary
*.pdf binary
# Explicitly NOT text, but still diffable with a converter
*.docx -text diff=astextplain
Specifications
- Seed
- 20260807
- Repository Name
- .gitattributes
- Rules
- 9
- Eol Values
- lf, crlf
- Uses Text Auto
- true
- Uses Binary Macro
- true
- Line Endings
- LF
- Encoding
- UTF-8
Testing contract
Expected to pass- Scenario
- Determine the checkout line endings for a .sh, a .bat and a .png under these attributes.
- Expected result
- The .sh file is checked out with LF, the .bat file with CRLF, and the .png is not normalised at all; the .docx is treated as binary for storage but diffable through astextplain.
What is a .gitattributes file?
A .gitattributes file assigns per-path attributes that change how Git handles matching files. It controls end-of-line normalisation (`text`, `-text`, `eol=lf`), diff and merge drivers, export filtering, `linguist-*` language hints, and Git LFS filters, using the same pattern syntax as .gitignore with attributes listed after each pattern.
How to use this file
Use an example .gitattributes file to test attribute parsers and repository-tooling that has to honour line-ending or diff-driver rules, verifying that binary paths are excluded from text normalisation and that later patterns override earlier ones.
How to use this file for testing
“Gitattributes - End-of-Line Normalisation Rules” is a deterministic Novus Examples fixture for Config parsing, Encoding detection, Config testing. TOML and INI configuration files with nested sections and typed values — for testing config parsers and loaders.
Documented properties for this file: seed 20260807 · UTF-8 · LF. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Diff and patch fixtures name their target paths and the exact edge case they exercise — rename, mode change, binary hunk, CRLF↔LF, or missing trailing newline. Apply or render them against the documented before-state; every author, path, and hash is fictional.
Point your config loader at the file and assert it reads the documented sections and typed values, including any deliberately-tricky nesting or comments.
Related files
- txtCODEOWNERS - Overlapping Globs With Documented WinnersDeliberately overlapping rules so every interesting path matches two or three of them, which is the only way to test that a resolver applies last-match-wins rather than most-specific-wins. One rule has no owners at all, which clears inherited ownership instead of adding any.
- gitattributesGitattributes - LFS Filters, Linguist Hints and export-ignoreThe non-EOL half of the format: LFS filter/diff/merge triples, `linguist-generated` and `linguist-vendored` hints that hide files from language statistics and review, `export-ignore` entries that drop paths from `git archive`, and a `merge=union` driver for an append-only changelog. Attribute values are unquoted and space-separated, so column alignment is whitespace a parser must collapse.
- gitconfigGitconfig - includeIf Conditions in Four FlavoursEvery conditional-include form git supports — path prefix, case-insensitive path prefix, branch glob, and a condition on an existing remote URL — plus one unconditional include. Order matters: a later include overrides an earlier one, so a parser that gathers includes into a set rather than a list resolves the wrong identity.
- gitconfigGitconfig - Sections, Quoted Subsections and Shell AliasesA realistic global config exercising the whole INI-like grammar: bracketed sections, quoted subsection names that are case-sensitive while section names are not, values with size suffixes, a shell alias whose leading `!` changes how the rest is executed, and both comment characters.
- gitignoreGitignore - Escaped #, !, Bracket and Trailing SpaceEvery escape the format defines, including the one nobody expects: a trailing space is stripped from a pattern unless it is backslash-escaped, so `draft\ ` and `draft` ignore different files. Editors that trim trailing whitespace on save silently change what this file means.
- gitignoreGitignore - Globstar, Anchors and Character ClassesOne pattern per rule in the gitignore grammar: a leading slash that anchors to the containing directory, the same name unanchored, `**` in all three positions, `?` and `[...]` classes, and a trailing slash that matches only directories. Every line is a separate assertion for a matcher's test suite.
Generated by generation/version_control.py. Free for any use, no attribution required — license.