-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Git Checkout Failed during clone or reset when there is illegal character from remote #2849
Comments
This is actually a known issue, and there have been valuable discussions around it already. In the most recent report, I wrote up a detailed analysis/project plan: #2803 (comment) It might make sense to continue our discussion in that ticket; To that end, I will mark this here ticket as a duplicate.
This sounds as if you had created that not necessarily just on "a Windows machine", but either using Cygwin's or MSYS2's shell tools. Cygwin (and by extension, the MSYS executables in MSYS2) use a trick to work around illegal file name characters: they are mapped into a private Unicode page, and that's what you are seeing here. Neither WSL nor regular Win32 tools (such as |
Nope.. I just cloned the repo from WSL Ubuntu and the resulting folder (shared between two systems via WSL) in Windows is committed and pushed. I have not installed cygwin or msys myself unless its something WSL does in the backend regarding files. So.. running the curl on ubuntu |
* Update puppet-keystone from branch 'master' to 4d17fb5dfb39b9f0f78635ce7560ee5900d9ab8a - Merge "Remove a file which causes cloning on Windows platform to fail" - Remove a file which causes cloning on Windows platform to fail There is a known issue with git-for-windows and currently clone and pull fail with invalid path errors if the target repository has any filename containing a character prohibited in Windows. We can find below examples reporting that issue. git-for-windows/git#2777 git-for-windows/git#2803 git-for-windows/git#2849 Because it is unlikely that the issue is solved in git-for-windows shortly, this change drops one release note file currently causing the failure, as a quick workaround. Note that we can't rename existing release note files because that would make notes appear in a wrong release, and this is why this change should remove that file. Change-Id: Ib3615761b366ed849177ae79d7d105ef8b839da4
There is a known issue with git-for-windows and currently clone and pull fail with invalid path errors if the target repository has any filename containing a character prohibited in Windows. We can find below examples reporting that issue. git-for-windows/git#2777 git-for-windows/git#2803 git-for-windows/git#2849 Because it is unlikely that the issue is solved in git-for-windows shortly, this change drops one release note file currently causing the failure, as a quick workaround. Note that we can't rename existing release note files because that would make notes appear in a wrong release, and this is why this change should remove that file. Change-Id: Ib3615761b366ed849177ae79d7d105ef8b839da4
Setup
defaults?
Any other interesting things about your environment that might be related
to the issue you're seeing?
Details
Powershell
Minimal, Complete, and Verifiable example
this will help us understand the issue.
Minimal
What did you expect to occur after running these commands?
What actually happened instead?
If the problem was occurring with a specific repository, can you provide the
URL to that repository to help us with testing?
The text was updated successfully, but these errors were encountered: