Support shallow clones
It would be nice if Gitkraken supported shallow clones.
At minimal, if it could detect that it is shallow clone and explained that or proposed to unshallow the clone (`git fetch --unshallow`), instead of just saying "Displaying 2000 commits, adjust in preferences" and showing nothing.
Comments: 4
-
28 Feb, '22
Julio WoosIn my current job, we have more than 30 repositories and some active for more than 5 years. To be able to use these repos with gitkraken, I have to do a full clone, but for almost all of they, I could use just a shallow copy, because its history isn't relevant for me.
These long repositories take some time to load, and it can be very annoying sometimes -
06 Nov, '22
Michael RansI have some repos with long histories which I don't need
-
13 Jun
CaseyThis would be very nice. I'm not able to use GK with a specific repo because it's over 150GB in size, over 45K tags, and 3K branches (growing every day). The only feasible way to work with this repo is to clone with a small depth as the majority of the repo is not useful to me. GK freezes quite a lot when I clone the repo without a depth and I have to wait several minutes just for it to respond after clicking on the tab for that repo. Since I cloned it with a depth, it's much more manageable but I can no longer view my changes in GK.
-
19 Sep
EldarIt would be a great feature for GitKraken! Clone/fetch/pull should automatically set specified depth for each request so that developers don't have to think about it. We have a lot of huge repos that my computer just can't handle if I clone them completely using GK.