Support for partial clone
When you have a repo with a very large history it can become quite big and it gets even worse if you have a lot of large binary files. Git LFS can be used to limit the size for binary files but it has its problems.
The partial clone added to Git can also solve this and it would be of great help to have support for this in GitKraken.
With partial clone you can specify to not download large files (git clone --filter=blob:limit=<size> ) or to only download the currently active revisions ( git clone --filter=blob:none). This can drastically reduce the download size. Other revisions are downloaded on demand.
With partial clone you still have everything in the repo, but you don't have to download everything. As opposed to sparse checkout you still have the entire history available, just not the blobs.
See https://docs.gitlab.com/ee/topics/git/partial_clone.html and https://git-scm.com/docs/partial-clone for more information.
Comments: 2
Oldest
•
Newest
•
Most likes
•
Fewest likes
-
01 Nov, '23
Adrianplease add this, I work on a repo that takes like 5Gb now with full depth but just something like 300mb when cloned with --filter=tree:0 and it would be pretty useful to have this feature
-
04 Feb
RichardFurther discussion of --filter=blob:none and how it differs from sparse and shallow:
https://github.blog/open-source/git/get-up-to-speed-with-partial-clone-and-shallow-clone
For many users this completely negates any need for git-lfs, and has very few downsides