fix: handle CRLF line endings properly #441
Open
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
- Add .gitattributes to enforce LF for shell scripts - Fix TeX Live package installation by removing CRLF from package names - Ensure consistent line endings across platforms
engynear
force-pushed
the
fix/crlf-line-endings
branch
from
a951d30 to
f1357f8
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.
Found an issue with line endings when building Dockerfile on Windows. Here's what happened and how I fixed it:
The problem:
What I did:
Added .gitattributes to handle line endings properly:
Fixed the TeX Live package installer by removing any \r characters from package names
Test results:
Let me know if you need any changes or have questions!