readme fix line endings to be LF not CRLF #268
Merged
Conversation
This file contains 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
davidbloss
approved these changes
Feb 28, 2024
|
Does this render any differently?? |
Not at all. But when viewing |
taimoorgit
force-pushed
the
ta/fix-readme-line-endings
branch
from
243d72e
to
cf88ca8
Compare
Co-authored-by: David Bloss <david@opslevel.com>
taimoorgit
force-pushed
the
ta/fix-readme-line-endings
branch
from
34b3543
to
66a59c4
Compare
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.
relies on #243
I noticed that for some reason, line endings were CLRF and not LF, and so that caused me a lot of trouble when I was trying to figure out why my git diff's were ending up being so massive and why GoLand was making diffs where each line I added ended with
^M.