Join the Webstudio community

Updated last month

Clone of Builder Fork Failed

At a glance

The community member is trying to self-host the Webstudio builder using the VSCode method, but is encountering issues when cloning their forked repository to their local machine. They have tried various troubleshooting steps, such as logging in and out of their GitHub account, setting up an SSH key, and cloning on a different machine, but the issues persist.

The comments suggest that the issue may be related to a private submodule in the repository, which is causing problems with cloning on both Mac and Windows. The community member was able to resolve the issue by deleting the private submodule directory through the GitHub web UI, after which the cloning process worked fine.

The answer provided by another community member suggests that using the Git CLI instead of the GitHub UI may be a better approach, as the GitHub UI is not the recommended way to interact with the repository.

Useful resources
So I am trying to self-host the builder using the VSCode method, and after forking webstudio to my github account, when I try to clone my fork onto my local computer, I get this error and I have tried most of the things already listed in there (logged out and back in, tried setting up an sshkey, etc) I do already have Docker (via OrbStack) and VSCode installed.

I am trying this on a MacMini (Apple Silicon with MacOS 15.3) if that matters
Marked as solution
Have you tried to use git via terminal. github ui is not the thing we are going to support
View full solution
B
P
I
39 comments
Github requires authentication into your account to clone repos. Perhaps git is not configured to connect with your account.
oh it is, I can clone other repos from my account (private and public ones)
I logged out and back into my github account twice in github desktop
I'm not sure then. You can try to fork the repo into your own account
Ah it's already a fork
that's what's making this weird
I understand if I were trying to clone the main repo, but why is it balking at my own fork
Maybe there is some restriction on your ssh key
I didn't have an SSH key until I got this error, then I went through the process of adding one thinking it might be required, but I'm getting this error whether I use regular email/password login or SSH auth
Does something about this repo require that I use SSH? maybe I messed that up since I just now tried doing it with SSH for the first time today (always just used email/pass auth for other github repos)
okay... so I just tried cloning it on my PC.. and the error is different...
could it be that this is also the issue on the Mac? I thought mac filenames could be much longer than Windows filenames
Https auth on github I think is just more restrictive and ssh just works from my experience.
Yeah, this looks like windows specific issue
We actually have this to test publishing πŸ™‚
So I deleted those files and commited (from github web UI) and now the windows github desktop gets stuck here:
MacOS cloning still doesn't work, gives same error
I guess I should delete that private-src as well since I can't access it?
which I can't do from the github webui... :-(
yeah I'm pretty sure that submodule is causing the issue in both mac and PC... is there any way to fix that?
yep, I deleted the whole directory on github web UI, and now the mac clones it perfectly. so that private submodule is causing the issue
would you guys be able to delete that or make it not private so that other people can fork / clone this project?
also should probably make that filename shorter for any windows people trying to clone this
Good catch. We will figure this out.
Have you tried to use git via terminal. github ui is not the thing we are going to support
Am I right that cloning is not working only in github ui app?
I'll try re-forking and recloning the main project again but with CLI to check, but does the Webstudio Builder require whatever is behind that private submodule to properly function? if so then it doesn't matter whether I use the desktop ui or git CLI...
Should work without it. We have checks on CI to make sure
yeah it clones fine with the git CLI, so I guess it was my fault all along πŸ˜…
sorry to waste y'alls time, you can delete this thread if you'd like
No problem. Now we know there is an issue with github ui
It might be 2 seperate issues - github ui hanging and also not successfully cloning when there is a private submodule
I was able to fix that with turning off "System OpenSSH", but instead of hanging, it just goes back to showing that "could not clone" error
as soon as I deleted that whole directory via github web ui, it cloned down with no errors
but regardless, it works fine from the beginning if you use git CLI
now to figure out why I can't get it to build with dev containers in VSCode on Mac
Add a reply
Sign up and join the conversation on Discord