-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Clone arguments --depth 1
not working with lg.callMain(['clone', url, dir, '--depth', '1'])
#52
Comments
Looks like I had some reading to do before opening this issue :) Just found that |
sorry for not seeing this before now, but thanks for going into the depths of this. I wasn't aware of the missing support for shallow clones myself. |
Shallow clone is now supported in libgit2 =) And btw, is there any solution to clone with |
wasm-git is now up to date with the latest libgit2 |
Where I can see api docs? I tried to use |
at this point wasm-git expose the examples from libgit2, and then you need to modify this file here: https://github.com/libgit2/libgit2/blob/main/examples/clone.c so that it can accept the depth argument ( or just set the however there's also a new cli in libgit2 that I would like to add support for and it seems it also does handle depth: https://github.com/libgit2/libgit2/blob/main/src/cli/cmd_clone.c CLI support is on my todo list. |
Currently trying to experiment the performance of
wasm-git
for not-so-small Git repositories, but using--depth 1
on aclone
call doesn't seem to have any effect. Any idea what could be happening?What I did was I modified the
githttpserver
to not add an Authorization header to HTTP requests and used Isomorphic Git's CORS proxy to bypass CORS restrictions to GitHub. So from mylocalhost
, I try to download any fairly-sized GitHub repository, and it takes forever, even with--depth 1
.Let me know if I can help fixing this!
The text was updated successfully, but these errors were encountered: