Skip to content

docs: use unix line-endings for markdown files#1144

Merged
klauspost merged 5 commits into
klauspost:masterfrom
thaJeztah:line_endings
Apr 30, 2026
Merged

docs: use unix line-endings for markdown files#1144
klauspost merged 5 commits into
klauspost:masterfrom
thaJeztah:line_endings

Conversation

@thaJeztah

@thaJeztah thaJeztah commented Apr 21, 2026

Copy link
Copy Markdown
Contributor

We noticed some churn in our CI where files ended up with the wrong line endings; opening this PR for consideration (I realise it's a large amount of "lines" changed, but hopefully a one-time rip of the bandaid is OK).

Summary by CodeRabbit

  • Chores
    • Added a .gitattributes rule to standardize markdown file line endings.
    • Normalized line endings across multiple README files.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
@coderabbitai

coderabbitai Bot commented Apr 21, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

The pull request standardizes line endings across markdown documentation by adding a .gitattributes rule to enforce LF line endings for all *.md files, then reformats existing README files in dict/, fse/, and huff0/ directories to comply with this standard. No functional or API changes are introduced.

Changes

Cohort / File(s) Summary
Git Configuration
.gitattributes
Added rule to enforce LF line endings (eol=lf) for all markdown files.
Documentation Reformatting
dict/README.md, fse/README.md, huff0/README.md
Normalized line endings from CRLF to LF across markdown documentation. Content remains unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly and accurately describes the main change: converting markdown files to Unix line endings, which is the primary objective evident in all modified files and the .gitattributes addition.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
huff0/README.md (1)

43-43: Minor typo: "some of there" → "some of these".

While touching this file, you might consider fixing this pre-existing grammar error.

📝 Suggested fix
-As can be seen above some of there are errors that will be returned even under normal operation so it is important to handle these.
+As can be seen above some of these are errors that will be returned even under normal operation so it is important to handle these.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@huff0/README.md` at line 43, Typo in README.md: replace "some of there are
errors" with "some of these are errors" (or rephrase to "some of these errors
will be returned") in the sentence that currently reads "As can be seen above
some of there are errors that will be returned even under normal operation so it
is important to handle these." to correct grammar and optionally add commas for
clarity.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@huff0/README.md`:
- Line 43: Typo in README.md: replace "some of there are errors" with "some of
these are errors" (or rephrase to "some of these errors will be returned") in
the sentence that currently reads "As can be seen above some of there are errors
that will be returned even under normal operation so it is important to handle
these." to correct grammar and optionally add commas for clarity.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 2f872549-63ef-4bee-bbd8-54cc6530c57e

📥 Commits

Reviewing files that changed from the base of the PR and between 1b63f2f and e04cf87.

📒 Files selected for processing (5)
  • .gitattributes
  • README.md
  • dict/README.md
  • fse/README.md
  • huff0/README.md

@klauspost

Copy link
Copy Markdown
Owner

We noticed some churn in our CI where files ended up with the wrong line endings

What do you mean?

@thaJeztah

Copy link
Copy Markdown
Contributor Author

Maybe @maxcleme recalls the exact details (it's in one of our internal repositories, where I noticed an extra job was added to fix line endings).

@thaJeztah

Copy link
Copy Markdown
Contributor Author

I should add that in general, vendored files should always be considered "opaque", so not sure if that job should be there in the first place, but I think LF is more commonly used for Markdown, so thought it was worth opening a pull request for consideration 😅.

@maxcleme

Copy link
Copy Markdown

We had vendoring issue in the past with dependabot PR when tied to windows-specific dependencies that forced us to use the following as a workaround:

      - name: Convert files in vendor folder to Unix format
        run: |
          find vendor -type f -print0 | xargs -0 dos2unix

After a quick search, looks like it is already reported but not fixed yet. dependabot/dependabot-core#8693

@klauspost klauspost merged commit ac2f5e8 into klauspost:master Apr 30, 2026
22 checks passed
@thaJeztah thaJeztah deleted the line_endings branch April 30, 2026 16:36
@thaJeztah

Copy link
Copy Markdown
Contributor Author

Thanks!

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.

3 participants