Repository navigation
chore: Enforce LF line endings via .gitattributes and .editorconfig - #980
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The configuration changes match the stated purpose and have no identified blocking issues.
0 open findings
What changed in this PR
Standardizes line endings across contributor environments and adds shared editor settings.
Changes:
- Enforces LF line endings for text files through Git.
- Adds EditorConfig settings for encoding and whitespace, preserving Markdown trailing spaces.
- Excludes
.editorconfigfrom distribution archives.
| File | Description |
|---|---|
.gitattributes |
Enforces LF and excludes .editorconfig from archives. |
.editorconfig |
Sets UTF-8, LF, final newlines, and whitespace rules. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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
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.
Summary
Line endings were left to each contributor's local
core.autocrlfsetting, since.gitattributesonly containedexport-ignorerules and there was no.editorconfig..gitattributes: add* text=auto eol=lfso text files are stored and checked out as LF on every OS..editorconfig(new): LF, UTF-8, final newline and trailing-whitespace trimming (disabled for Markdown, where trailing spaces are significant)..editorconfigis added toexport-ignoreso it stays out of dist archives.All tracked files were already LF, so
git add --renormalize .produced no content changes.docs/is left untouched as it is expected to be removed in a follow-up PR.🤖 Generated with Claude Code