zostera / django-marina / 38132229553

100%

push

github

Enforce line endings in git, and stop .editorconfig contradicting ruff (#699)

Two changes, both following the same line: the repository enforces what it
needs to guarantee, and stops telling people how to configure their editor.

.gitattributes with `* text=auto` is the guardrail .editorconfig could not be.
It has declared end_of_line = lf since the beginning and it has not held:
django-bootstrap4 has a CRLF file in src/ right now, and django-bootstrap5 had
to fix the same file by hand in 26.4. text=auto normalises on the way in, so a
commit from a machine with CRLF stores LF regardless of anyone's editor. Not
eol=lf, which would also dictate the working tree. What the repository stores
is the repository's business; what a checkout looks like on someone's machine
is theirs. Nothing here renormalises, marina was already clean.

.editorconfig loses its [*.py] section. It set max_line_length = 88, inherited
from Django, which pairs that with black's default of 88. We use ruff at 120.
So an editor honouring the file wrapped Python at 88 and flagged more than a
thousand lines across the five packages that lint is perfectly happy with. ruff
owns Python layout; the advisory file should not hold a second opinion on it.

The rest of .editorconfig stays. It still speaks for TOML and YAML indentation,
rst line length and charset, where nothing else does, and that is the part
worth having: a courtesy to contributors rather than a rule with no teeth.

PACKAGING.md lists .gitattributes as synced identically, since it takes no
per-package value.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

28 of 28 branches covered (100.0%)

Branch coverage included in aggregate %.

164 of 164 relevant lines covered (100.0%)

15.0 hits per line