-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Fixes Git Clone Problem with Spaces #60573
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good @scottymcraig
I realise my bug report describes spaces, but having seen the fundamental problem (the name can contain characters not allowed in a file path) surely you would fix it like this |
Because encoding a string that already has encoding can cause it to be re-encoded. We just simply want to catch the cases where it comes from Azure DevOps with the spaces. None of the other cloning urls are having problems. |
Yes and I've just checked, Azure DevOps won't allow any other toxic characters. Just being paranoid! :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we don't really need to check whether the url contains a space. It will be more better, if we are encoding the url even if it is not contains a space.
@MrJithil We can't do that - see my comment above Peter's |
Can't wait for this issue to be fixed :) |
Thought exactly the same as @PeterWone but I do like the reasoning from @scottymcraig. Thanks for the fix! |
Fixes #60472. Checks to see if there are spaces in the URL and if so, encodes them.