chore: ensure all text files end with a single blank newline #567
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.
While we have this captured with
.editorconfig
which is supported by a lot of editors, it's very easy to miss in the review UI and in VSCode in particular requires an extension to be installed meaning people need to be aware it's a thing; so this setups up CI to explicitly check and warn about this.Unsurprisingly this has revealed a handful of files that have extraneous end-of-file newlines, most of which are in test files though I don't think they're actually critical to the test so I have removed them - the only ones I've ignored are two that are explicitly covering behaviour when there are trailing newlines, though I actually suspect it would be fine to have just a single newline at the end of the file, which would be nice at it would let us avoid needing a
.linelint
config, but for now I've just ignored them