Skip to content
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

Install from git may be slow when cloning huge repository #2412

Open
2 tasks done
Inndy opened this issue May 13, 2020 · 3 comments
Open
2 tasks done

Install from git may be slow when cloning huge repository #2412

Inndy opened this issue May 13, 2020 · 3 comments
Labels
kind/feature Feature requests/implementations status/triage This issue needs to be triaged

Comments

@Inndy
Copy link

Inndy commented May 13, 2020

  • I have searched the issues of this repo and believe that this is not a duplicate.
  • I have searched the documentation and believe that my question is not covered.

Feature Request

Install from git should not clone all commit history. Can we just make a shallow clone instead?

@Inndy Inndy added kind/feature Feature requests/implementations status/triage This issue needs to be triaged labels May 13, 2020
@markopy
Copy link

markopy commented Feb 22, 2021

+1 for this.

It makes sense to just check out the branch actually needed and without all the history. This can reduce the cloning time enormously for large repositories with a lot of history.

This seem like it would be a fairly simple change with something like this added to the git invoke:

--branch <rev> --single-branch --depth 1

@Kache
Copy link

Kache commented Sep 9, 2022

Ran into this exact issue here: #2094 (comment)

@gaborfekete-greehill
Copy link

I had a similar issue when a branch used submodules and the other not, and the non-default would have been the preferred one: #9612

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Feature requests/implementations status/triage This issue needs to be triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants