fix: ensure posix-compliant newline at end of generated configs #170
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
JoshuaKGoldberg
approved these changes
May 14, 2025
There was a problem hiding this comment.
👍 I'm in favor of this. The classic https://stackoverflow.com/questions/729692/why-should-text-files-end-with-a-newline links to the POSIX spec that defines:
3.206 Line
A sequence of zero or more non- characters plus a terminating character.
Merged
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.
This PR addresses the missing end-of-line (EOL) at the end of generated config files. By ensuring a proper newline is present, it maintains POSIX compliance and prevents editors from introducing unintended changes due to the absence of a final EOL.