Repository navigation
docs: explain Git Bash path conversion workaround - #10777
Open
Mr-KnightCLI wants to merge 1 commit into
Open
Mr-KnightCLI wants to merge 1 commit into
Mr-KnightCLI wants to merge 1 commit into
Conversation
This branch has not been deployed
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.
Description
Documents that Git Bash on Windows may convert slash-prefixed command-line values into filesystem paths before AWS CLI receives them, and shows how to disable conversion for one command with
MSYS_NO_PATHCONV=1. This provides a workaround for the behavior reported in #10769.Validation
Manually checked the reStructuredText section and command example. This is a documentation-only change; no tests were run.