Introduce end-of-line normalization #2637
Merged
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
…faq/external-client/model-sample Changes to be committed: modified: documentation/staging/content/faq/external-clients.md
Signed-off-by: galiacheng <haixia.cheng@microsoft.com>
tbarnes-us
approved these changes
Nov 23, 2021
rjeberhard
approved these changes
Nov 23, 2021
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.
We have lots of shell script in samples folder, it 's easy to run into LF ending issue if customer working with Windows WSL, see #2636
This pr contains:
TwoWaySSLEnabledname in documentation/staging/content/faq/external-clients.mdThe customer should checkout all .sh and .py files with LF ending in different platforms.
If you have local .gitattributes, please run the following command to refresh files endings.