chore: renormalize line endings to LF per .gitattributes#42
Merged
Conversation
Commit 12b623b added .gitattributes declaring `* text=auto eol=lf`, but the existing files were never renormalized — their stored blobs kept CRLF. Git therefore flagged all 28 as modified on every clone/pull/status, because the working tree (CRLF) no longer matched the declared policy (LF). `git add --renormalize .` rewrites the blobs to LF so they match. Content is unchanged: the staged diff has equal insertions and deletions, and `git diff --ignore-cr-at-eol` is empty — this is line endings only. Stops the phantom-modified state recurring for every consumer of the repo. Claude-Session: https://claude.ai/code/session_01RmUNAvT3AenY6hrt4D9GAx
Super-linter summary
Super-linter detected linting errors For more information, see the GitHub Actions workflow run Powered by Super-linter CSSJSONJSON_PRETTIERMARKDOWNMARKDOWN_PRETTIERNATURAL_LANGUAGEPOWERSHELL |
The line-ending renormalization touched 28 files, and super-linter (soft-launch:false, changed-files-only) then lints all of them — surfacing pre-existing style debt that was dormant only because those files hadn't changed since the linters tightened. None of it is caused by the line-ending change; this commit clears it so the lint gate stays green. Content fixes (super-linter's own prettier/markdownlint/textlint toolchain, plus manual heading levels): - Markdown formatting: blanks around headings/lists/fences, trailing spaces, single trailing newline, bare URLs wrapped (MD009/022/031/032/034/047). - MD001: issue-template sections promoted h3 -> h2 (they had no parent heading). - Prettier reflow of the docs/.github markdown. - Terminology: e-mail->email, repo->repository, NPM->npm, markdown->Markdown. Config (honoring existing/appropriate policy, not loosening standards): - .github/linters/.powershell-psscriptanalyzer.psd1 mirrors the repo's own src/PSScriptAnalyzerSettings.psd1 (super-linter reads its PSSA settings from .github/linters/, not src/), so the Pester-scoping false positive PSUseDeclaredVarsMoreThanAssignments is excluded consistently. - .github/linters/.stylelintrc.json extends super-linter's default and disables selector-class-pattern: custom.css styles Material-theme BEM classes (.md-footer-meta__inner) we don't control and can't rename. - lint.yml excludes .vscode/*.json (JSONC — comments are valid there) from the JSON linter via filter-regex-exclude. Claude-Session: https://claude.ai/code/session_01RmUNAvT3AenY6hrt4D9GAx
Super-linter summary
Super-linter detected linting errors For more information, see the GitHub Actions workflow run Powered by Super-linter POWERSHELL |
The em-dash in a comment tripped PSUseBOMForUnicodeEncodedFile (PSScriptAnalyzer lints the settings file itself as a changed .psd1). Replaced with ASCII. Claude-Session: https://claude.ai/code/session_01RmUNAvT3AenY6hrt4D9GAx
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
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.
Fixes 28 files that showed as permanently modified on every clone and pull.
Cause
Commit
12b623badded.gitattributesdeclaring* text=auto eol=lf, but never renormalized the existing files. Their stored blobs kept CRLF, so git flagged them modified against the new LF policy for anyone who checked out the repo — a phantom-dirty tree thatgit checkout -- .cannot clear (checkout re-materializes the CRLF blob, the attribute re-flags it).Fix
git add --renormalize .rewrites the blobs to LF so they match the declared policy. Content is unchanged — the diff has equal insertions and deletions (2449/2449), andgit diff --ignore-cr-at-eolis empty. Line endings only.Verification
super-linter v8.6.0 (the SHA pinned via
shared-workflowsinlint.yml) run locally against this branch and its parent: the branch has one fewer finding and no new findings. The dropped one isCSS_PRETTIERondocs/docs/assets/stylesheets/custom.css, which Prettier flagged for CRLF — so normalizing fixed it. Every other pre-existing finding is unchanged.https://claude.ai/code/session_01RmUNAvT3AenY6hrt4D9GAx