Git partial clone lets you fetch only the large file you need
about.gitlab.com
Git partial clone lets you fetch only the large file you need
1–10 of 88 posts
Re: Git partial clone lets you fetch only the large file you need
#2> One reason projects with large binary files don't use Git is because, when a Git repository is cloned, Git will download every version of every file in the repository.
Wrong? There's a --depth option for the git fetch command which allows the user to specify how many commits they want to fetch from the repository
Re: Git partial clone lets you fetch only the large file you need
#3> One reason projects with large binary files don't use Git is because, when a Git repository is cloned, Git will download every version of every file in the repository. Wrong? There's a --depth option for the git fetch command which allows the user to specify how many commits they want to fetch from the repository
Yes, but 95% of devs, even fairly talented ones, don't really know how to use Git.
Re: Git partial clone lets you fetch only the large file you need
#4This is great. We use get lfs extensively, and one of the biggest complaints we have is users have to clone 7GB of data just to get the source files. There's a work around in that you don't have to enter your username and password from the lfs repo, and let it timeout, but that's a kluge.
Re: Git partial clone lets you fetch only the large file you need
#5> One reason projects with large binary files don't use Git is because, when a Git repository is cloned, Git will download every version of every file in the repository. Wrong? There's a --depth option for the git fetch command which allows the user to specify how many commits they want to fetch from the repository
depth just let you control the amount of history. It will not let you exclude files that are at the highest depth that you don't want. So while that statement was not accurate, it's not what this feature is intended for.
Re: Git partial clone lets you fetch only the large file you need
#6> One reason projects with large binary files don't use Git is because, when a Git repository is cloned, Git will download every version of every file in the repository. Wrong? There's a --depth option for the git fetch command which allows the user to specify how many commits they want to fetch from the repository
Yes, but 95% of devs, even fairly talented ones, don't really know how to use Git.
Author seems to be a manager, not necessarily a dev.
Re: Git partial clone lets you fetch only the large file you need
#7Has anyone used Git submodules to isolate large binary assets into their own repos? Seems like the obvious solution to me. You already get fine-grained control over which submodules you initialize. And, unlike Git LFS, it might be something you’re already using for other reasons.
Re: Git partial clone lets you fetch only the large file you need
#8Also --reference (or --shared) is a good parameter to speed-up cloning (for build, for example), if you have your repository cached in some other place.
I was using it a long time ago when I was working on system that required to clone 20-40 repos to build. This approach decreased clone timings by an order of magnitude.
Re: Git partial clone lets you fetch only the large file you need
#9Has anyone used Git submodules to isolate large binary assets into their own repos? Seems like the obvious solution to me. You already get fine-grained control over which submodules you initialize. And, unlike Git LFS, it might be something you’re already using for other reasons.
The problem with git submodules is they can't be used like a hyperlink to another repository. Updating the submodule requires updating the superproject as well. The new commits are invisible to the superproject until that is done.
It'd be great if they worked like Python's editable package installations.
Re: Git partial clone lets you fetch only the large file you need
#10In AWS, it's worth considering putting those large files in an S3 bucket.