chore: pin line endings before this repo drifts the way minecraft did - #41
Open
MorningLightMountain713 wants to merge 1 commit into
Open
MorningLightMountain713 wants to merge 1 commit into
MorningLightMountain713 wants to merge 1 commit into
Conversation
MorningLightMountain713
force-pushed
the
chore/normalise-line-endings
branch
from
September 5, 2026 14:57
bc3a0b3 to
507de74
Compare
Nothing to convert - all 130 text files here are already LF. That is luck, not a rule: there is no .gitattributes, so the repo depends on every contributor having core.autocrlf set the way this one happens to need it. minecraft-server-website is the same codebase without that luck. Its root commit went in from a Windows machine and 36 of its 118 files have been CRLF ever since, including the ServerTerminal.jsx that is this repo's twin. .gitattributes is fluxos-frontend's, verbatim - the same web-project template already in use across the org. `* text=auto` normalises text to LF in the repository whatever a contributor's machine writes locally, and the eol= overrides go both ways: .bat, .cmd and .ps1 pinned to CRLF because Windows needs it, .sh, .husky/* and package.json pinned to LF because a shell script or a hook with CRLF does not execute. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
MorningLightMountain713
force-pushed
the
chore/normalise-line-endings
branch
from
September 6, 2026 16:41
507de74 to
d9e6c07
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
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.
A
.gitattributesso this repo cannot drift the wayminecraft-server-websitedid. Nothing to convert and no code changes.Stacked on #40 — it must merge first.
Why, when nothing is broken here
All 130 text files in this repo are already LF. That is luck, not a rule: there is no
.gitattributes, so the repo depends on every contributor havingcore.autocrlfset the way it happens to need.minecraft-server-websiteis the same codebase without that luck. Its root commit went in from a Windows machine and 36 of its 118 files have been CRLF ever since — including theServerTerminal.jsxthat is this repo's twin, and the file both these PRs change.What that costs over there: writing that file back as LF while making the same 78-line change produced a 1,609-line diff which buried the real change. One editor with different settings, or one formatter run, does the same thing here on the day someone commits from Windows.
What this does
.gitattributesisfluxos-frontend's, verbatim — the same web-project template already in use across the org, 207 lines.* text=autois the line that does the work: text is normalised to LF in the repository whatever a contributor's machine writes locally. Theeol=overrides go both ways —.bat,.cmdand.ps1pinned to CRLF because Windows needs it,.sh,.husky/*andpackage.jsonpinned to LF because a shell script or a git hook with CRLF does not execute. 59binaryrules stop git touching line endings inside images and fonts.git add --renormalize .was run and changed nothing, which is the point: this is a guard, not a repair.🤖 Generated with Claude Code