-
Notifications
You must be signed in to change notification settings - Fork 365
-
Notifications
You must be signed in to change notification settings - Fork 365
Unable to clone repository on Windows #205
Comments
Hi Brendan – thanks for flagging this! You may have seen it already, but this wiki article looks as if it might be useful: However, it does look a bit like this may be a problem with the scratch-curriculum repo… What do you think, @shiftkey? |
@andylolz it's an unfortunate limitation of the tooling in it's current state - you can create files on disk in Windows with paths that contain Unicode characters. I'll get in touch with the msysgit team about this as well, but I fear their priorities are on porting Git v2 to Windows. |
Great – thanks. Keep us posted on their response. It’s interesting that it’s just these two files that appear to break, and not the many other unicode filenames in the repo… I wonder if it’s unrelated to unicode characters, and instead related to the trailing space in the directory name? Total guess! I’ve just renamed the directory to remove that trailing space – would you try |
P.S. 8a45c69 suggests there’s definitely some sort of funny business going on here! I’m not sure why |
So I was able to workaround this error by following these instructions:
So I think something specific to cloning is triggering the issue. Thanks for nudging me to explore further! |
whoa – that’s even weirder! I’m surprised that works, but I’m just testing on a windows box now. Taking a while – this repo is way too big… |
Okay – I managed to recreate the error on a windows box by cloning the repo before 8a45c69 (the
…I then started again, and cloned the current
…so I’m concluding that 8a45c69 fixed the issue :) You can try confirming this by re-cloning Thanks for reporting this, @shiftkey! |
I am facing the same thing, someone pushed "somedir /main.js". and breaks cloning in Windows, so, just renaming the folder should fix the issue? |
Also, is there a way to setup .gitignore to ignore directories like that for sake of compatibility? |
Are you talking about this repo, @ronnyfm? Or a different one? |
Sorry, I realized after I commented that this was a very specific discussion hehe, but I was talking about a different repo where many directories were pushed with trailing spaces, I've fixed it now, and added this in .gitgnore to prevent future mistakes: |
Are we able to remove the special characters in these files?
EDIT: I don't mind submitting a PR to address the technical problem, but I'd love some pointers on how best to go about it to maintain i18n for these cultures...
The text was updated successfully, but these errors were encountered: