Skip to content

chore: normalize line endings on test_context_window_events.py#183

Merged
jrob5756 merged 1 commit into
mainfrom
chore/normalize-line-endings
May 13, 2026
Merged

chore: normalize line endings on test_context_window_events.py#183
jrob5756 merged 1 commit into
mainfrom
chore/normalize-line-endings

Conversation

@jrob5756
Copy link
Copy Markdown
Collaborator

The blob for tests/test_engine/test_context_window_events.py was stored in the index with CRLF, but .gitattributes declares *.py text eol=lf. The mismatch caused git status to flag the file as modified on every fresh checkout — the working-tree CRLF copy doesn't match what git would store on add after normalization, so the diff is permanently non-empty until the index blob itself is rewritten.

Fix

git add --renormalize tests/test_engine/test_context_window_events.py

Pure CRLF→LF renormalization — verified zero content changes:

$ git diff --cached --ignore-cr-at-eol tests/test_engine/test_context_window_events.py
$ # (empty)

After this lands, future git pull / git checkout produce LF and git status stays clean for everyone.

Why only this file

git ls-files --eol | awk '$1 == "i/crlf" && $3 ~ /eol=lf/' returns just this one path — every other *.py file is already correctly stored as LF.

This file's blob in the index was stored with CRLF, but .gitattributes
declares `*.py text eol=lf`. The mismatch caused `git status` to flag
the file as modified on every fresh checkout (the working-tree CRLF
copy didn't match what git would store on `add` after normalization).

Renormalized via `git add --renormalize`. No content changes — verified
with `git diff --cached --ignore-cr-at-eol` (empty diff). After this
commit, future checkouts produce LF and the file stays clean.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@jrob5756 jrob5756 merged commit 008b17c into main May 13, 2026
3 checks passed
@jrob5756 jrob5756 deleted the chore/normalize-line-endings branch May 13, 2026 21:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant