Repository navigation
fix(repository): normalize generated README final newline - #432
Merged
Merged
Conversation
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.
Why
Generated READMEs can end with extra blank lines when an unlicensed repository has no license section.
Changes
Normalize only terminal LF bytes after template expansion so every generated README ends with one LF.
Cover all license states, preserved license assets, both documentation-index settings, and repeat-generation stability.
Validation
The expected failing test reproduced three trailing LF bytes for the unlicensed fixture.
On Windows, all 24 repository unit tests passed after the change.
Strict Clippy for all
dotfilestargets, workspace formatting, andgit diff --checkpassed on Windows.Kani and native verification on other platforms weren't run.
Closes #428.
@coderabbitai ignore