Anything that reviews, applies, or renders a change needs a diff it did not produce itself. This category carries unified diffs and git-format patches across the cases that break naive parsers: renames, binary hunks, file modes, added and deleted files, CRLF-versus-LF changes, no-newline-at-end-of-file markers, and multi-file series. Conflict fixtures ship the three-way marker layout so merge tooling can be tested without staging a real merge. Alongside them sit the configuration files every repository carries (.gitignore, .gitattributes, .gitconfig, .gitmodules) plus commit-message and changelog samples for conventional-commit linters. Every path, author, and hash is fictional and deterministic, so a patch applies the same way on every machine.
Filter version control on Browse · 88 files · 5 subcategories
Results start with a representative from each related test family. Use a card’s variant menu or the filters below to reach a specific format, profile, or failure case; every sample retains its own detail page and download.
Renames, file-mode changes, binary hunks, added and deleted files, CRLF↔LF changes, no-newline-at-end-of-file markers, and multi-file patch series.
The patch fixtures are self-consistent unified diffs with documented target paths, so they apply cleanly against the stated before-state. Conflict fixtures ship the three-way marker layout instead, for merge tooling.
No. Every author, path, hash, and timestamp is fictional and deterministic, nothing here is extracted from a real repository.
Start with one example from each use-case group, then continue through its other test families. Choose a use case, search, or filter to find a specific profile; a card’s variant menu contains its related samples.
58 test families · 88 available files · Page 1 of 4
Diffs
The same change as the unified twin, emitted in the pre-unified context format: `*** before` and `--- after` blocks separated by a row of asterisks, with `!`, `+` and `-` change markers. Parsers that assume every diff st
History
The machine-generated twin of the hand-written changelog: version headings that are themselves compare links, a leading warning glyph on the breaking-changes section, and every entry ending in a short-hash link back to t
Merges
What `git show` prints for a merge commit: a `diff --cc` header, an index line naming three blobs, `@@@` hunk markers, and two prefix columns instead of one. The `++` line is the giveaway a reviewer is looking for: conte
Patches
The `--cover-letter` message git writes ahead of a series: a `[PATCH 0/3]` subject, a shortlog of the authors and their subjects, and the combined diffstat, but no diff of its own. Series tooling has to recognise it as m
Repo Config
An intentionally invalid ownership file carrying five defects that all parse as plausible lines: an owner that is neither a handle nor an email, a team with no organisation, a character class, a negation, and a path with
Diffs
A one-line file changed in place. Both ranges have length one, so the header is written `@@ -1 +1 @@` with no comma and no count: the abbreviation the unified format allows and that regexes of the form `-(\d+),(\d+)` fai
History
A breaking change announced twice, which the specification allows: a `!` after the scope and a `BREAKING CHANGE:` footer whose value continues onto a second line. Generators that stop a footer at the first newline lose h
Merges
The same conflict with `merge.conflictStyle=diff3`, which inserts the merge base between the two sides behind a row of pipes. Tools that split a conflict on `=======` alone silently fold the ancestor text into the ours s
Patches
The `index` line abbreviates both blob ids to seven characters, which is what plain format-patch emits and what most patches in the wild carry. Three-way application can still fall back to path matching, but the blobs ca
Repo Config
Deliberately 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,
Diffs
Byte-for-byte the same diff as its LF twin except that every line ends CR LF, which is what a diff produced or saved on Windows looks like. Readers that compare a hunk line against expected content without stripping the
History
The stable machine format of git blame: a full header block the first time a commit appears and a bare `<sha> <old> <new>` line every time after, with each source line following on a tab-prefixed line. A parser that expe
Merges
Someone committed a file that still contained conflict markers, and merging that commit produced markers inside markers. Region matchers that pair the first `<<<<<<<` with the first `=======` split this file in the wrong
Patches
The commit message uses `---` as a horizontal rule, so the file contains two lines that look like the diffstat separator. git's own mailinfo ends the message at the FIRST one, which quietly truncates the message and drop
Repo Config
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 th
Diffs
The mirror of the added-file fixture: every line is a deletion and the new range is `+0,0`. A renderer that writes an empty file instead of unlinking it, or that reports the change as a truncation, fails this one.
History
Per-commit file lists with single-letter status codes, tab-separated. Rename rows are the trap: `R100` is followed by TWO paths instead of one, so a splitter that takes field 2 as the filename reports the old path for re
Merges
Documentation about merge conflicts that quotes the markers inside a fenced code block, and then genuinely conflicts further down. A pre-commit hook that greps for `^<<<<<<<` reports two hits and blocks a clean commit; o
The use-case group filter replaces the long list of category sections.
