fix(transport): correctly parse Windows drive-letter paths as file en… #1710
+37
−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.
This PR fixes issue #1621 where local Windows paths (e.g., C:/... or C:...) were incorrectly parsed as SCP/SSH endpoints, causing go-git to attempt SSH connections for local repositories.
Changes
Added a platform-specific guard to prevent Windows drive-letter paths from being treated as SCP-like.
Ensured that such paths are parsed as file endpoints.
Added a Windows-only regression test (transport_windows_test.go) to verify that [NewEndpoint("C:/...")] and [NewEndpoint("C:\...")] return protocol "file".