Enforce LF line endings: .gitattributes + ruff format settings - #17
Merged
Conversation
The repo was 123 files LF with 4 Python files mixed/CRLF and nothing enforcing endings. Add .gitattributes (* text=auto eol=lf, .are fixtures protected as binary), ruff format line-ending=lf, and renormalize the four offenders to LF. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01F8kWxXQUY73XMXyeUYhkLd
ctoth
force-pushed
the
chore/enforce-lf-endings
branch
from
July 27, 2026 06:39
cd94f36 to
4acc3ea
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds line-ending enforcement the repo previously lacked (no
.gitattributes, no ruff config,core.autocrlf=false), which had let four Python files drift to mixed/CRLF endings against the repo's 123-file LF convention..gitattributes:* text=auto eol=lf;*.are -textso the MUD area fixtures (test/rom/*.are) stay byte-exact — they are test data and must never be renormalized.pyproject.toml:[tool.ruff]with[tool.ruff.format] line-ending = "lf".area_reader/__init__.py,area_reader/constants.py,conftest.py,test_area_reader.py.Verification: after the change
git ls-files --eolshows every tracked text file asi/lf, with only the two protected.arefixtures non-text; full suite940 passed in 69.55s(identical count to master — no content change).Note on merge order: #16 touches
constants.pyandtest_area_reader.pywith the current (pre-normalization) endings. Merge #16 first, then I'll rebase this branch over master so the renormalization covers its additions; merging this first will make #16 conflict on every line of those files.🤖 Generated with Claude Code
https://claude.ai/code/session_01F8kWxXQUY73XMXyeUYhkLd