patch488 B

Git Patch - Mode Change With No Hunks

A permission change and nothing else: the file section has `old mode`/`new mode` headers, no `index` line, no `---`/`+++` pair and no hunks at all. Parsers that require at least one hunk per file drop this change entirely and report an empty patch.

Visual diff / regression Code parsing Editor testing

Preview — first 18 linespatch

From ad17cdbedf59e0bcac6247b6bffb9d4389b99dc4 Mon Sep 17 00:00:00 2001
From: Ada Fernsby <ada.fernsby@example.invalid>
Date: Thu, 5 Mar 2026 08:20:11 +0000
Subject: [PATCH] chore: make release.sh executable

It has been chmod +x in everyone's checkout for a year.
---
 scripts/release.sh | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 mode change 100644 => 100755 scripts/release.sh

diff --git a/scripts/release.sh b/scripts/release.sh
old mode 100644
new mode 100755
-- 
2.43.0

Specifications

Seed: 20260807
Extended Header: old mode / new mode
Files: 1
Hunks: 0
Old Mode: 100644
New Mode: 100755
Line Endings: LF
Encoding: UTF-8

Testing contract

Expected to pass

Scenario: Parse a patch whose only file section contains no hunks.
Expected result: One file section is reported for scripts/release.sh with a mode change 100644 to 100755 and zero hunks — not an empty patch.

What is a .patch file?

A .patch file is a unified diff packaged for transmission, most often as produced by `git format-patch`. Beyond the diff itself it carries an email-style header with the author, date, and commit subject, a commit message body, per-file `diff --git` headers recording renames and mode changes, and hunk headers of the form `@@ -old,count +new,count @@`. Applying it reconstructs a specific change against a specific before-state.

How to use this file

Use an example .patch file to test patch application, code-review renderers, and diff parsers — exercising renames, mode changes, binary hunks, added and deleted files, and the `\ No newline at end of file` marker that naive parsers silently drop.

How to use this file for testing

“Git Patch - Mode Change With No Hunks” is a deterministic Novus Examples fixture for Visual diff / regression, Code parsing, Editor testing. A/B image twins with controlled pixel changes, anti-alias variants, and UI chrome crops for screenshot diff and visual regression tools.

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.

Treat A/B twins as a visual regression unit: run your pixel or perceptual diff, assert a non-zero delta on the changed twin, and keep thresholds calibrated against the documented change kind in specs.