Set LF-only (\n) line endings for .sh files to fix #1905 #2181
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
|
Build size and comparison to main:
|
NeroBurner
reviewed
Jun 11, 2025
NeroBurner
approved these changes
Jun 12, 2025
Contributor
NeroBurner
left a comment
NeroBurner
left a comment
There was a problem hiding this comment.
LGTM, LF is the default on Linux, so this should have no impact on Linux user and will help WSL user
mark9064
approved these changes
Jun 16, 2025
JustScott
pushed a commit
to JustScott/InfiniTime
that referenced
this pull request
Jul 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Windows machines may fail to build the docker image with cryptic bash/
set -error messages if shell scripts are not checked out with unix-style line endings.Should fix #1905