This may be opinion rather than a bug (hence not submitted as a bug report), but when I was creating a new project by cloning from a GitHub repo, the UI wanted the clone directory to already exist (or at least that's how I interpreted the error message).
I would expect this to work like CLI git clone works, and to create the directory the repo files (and presumably the project files - this is my first project) live in as part of the clone operation. I.e., if I want a project cloned from sHtev/myrepo to live under ~/Code, I should be able to select that directory in the Clone window and my project to clone into ~/Code/myrepo. If this is the intent, then maybe this is a bug (Intel Mac user here).
This may be opinion rather than a bug (hence not submitted as a bug report), but when I was creating a new project by cloning from a GitHub repo, the UI wanted the clone directory to already exist (or at least that's how I interpreted the error message).
I would expect this to work like CLI
git cloneworks, and to create the directory the repo files (and presumably the project files - this is my first project) live in as part of the clone operation. I.e., if I want a project cloned fromsHtev/myrepoto live under~/Code, I should be able to select that directory in the Clone window and my project to clone into~/Code/myrepo. If this is the intent, then maybe this is a bug (Intel Mac user here).