Add Shell Script Handling to .gitattributes #2960 #2961
+1
−0
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When entrypoint.sh is edited on Windows, the file may end up with Windows-style line endings (CRLF).
This can cause the script to fail when the Docker container starts, because the shell inside the container expects Unix-style line endings (LF).
To prevent this, we should update .gitattributes to ensure all shell scripts use LF:
*.sh text eol=lf
This will guarantee that entrypoint.sh (and any other .sh files) work correctly in Docker environments regardless of the host OS.