NIAD-3477: Removing windows-native symbols that prevent the files being run as native bash scripts - #349
Merged
Merged
Conversation
…ative bash scripts
|
Images built and published to ECR using a Build Id of PR-403-d05e48e |
chiaramapellimt
approved these changes
Sep 4, 2026
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
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.
What
Removing windows-native symbols that prevent the files being run as native bash scripts
Why
Bash doesn't recognize files as runnable with Windows-native symbols hence this PR addresses it by removing those symbols
Type of Change
Please check the option(s) that apply.
Checklist