Replies: 3 comments
|
I retried this and created an empty project directory to clone into and got a gh error message: It seems like a) there should be a better user-facing message for the underlying command failing and b), the actual path selected is not being passed to |
|
you're supposed to put in the full path: CleanShot.2026-05-29.at.16.14.56.mp4open to adding support for cloning with inferred dir as another alternative |
|
PR #5989 implements this. The clone step now proposes the selected folder plus the repository folder, so picking A few niceties that came out of it:
|
Uh oh!
There was an error while loading. Please reload this page.
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).All reactions