Force line endings on *.sh files #31
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
Fix line endings for windows users. Do not allow user core.autocrlf to change the line endings for *.sh files. This will fix issues building container by removing the line endings on the shebang of the copied bash files.
|
This seemed to open a new issue, this commit is to resolve #30 |
|
Thanks for this! Sorry it took me almost a year to merge it! |
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.
Fix line endings for windows users. Do not allow user core.autocrlf to
change the line endings for *.sh files. This will fix issues building
container by removing the line endings on the shebang of the copied bash
files.
Users may need to delete all *.sh files, and then use
git restoreto update checked out files (another option for those that don't have changes is to delete and then clone the repo).