GitHub Community
Can I have my repo's Download ZIP option resolve LFS? #206617
🏷️ Discussion TypeQuestion BodyI've configured my repo to use LFS to handle images and a few other large binary files. While users can clone my repository fine, many decide to download the ZIP file from the code dropdown instead. I then get bug reports because the images are just text stubs. I have instructions in the README that they should clone with LFS, but a lot of users are ignoring that. Is there any way to configure the project so that the Download ZIP option has the LFS already resolved? |
Replies: 1 comment
|
Hi, GitHub's Download ZIP option normally downloads the repository's Git files, while Git LFS stores the actual large files separately. That's why LFS files can appear as text pointers instead of the original files. If you want users to receive the actual files, the best workaround is to ask them to clone the repository with Git LFS installed, or provide a separate release archive containing the files. I don't believe there is a repository setting that makes the standard Download ZIP option automatically resolve LFS files. It would be useful if GitHub offered that as an option, especially for repositories where users are expected to download assets without installing Git LFS. |
Hi,
GitHub's Download ZIP option normally downloads the repository's Git files, while Git LFS stores the actual large files separately. That's why LFS files can appear as text pointers instead of the original files.
If you want users to receive the actual files, the best workaround is to ask them to clone the repository with Git LFS installed, or provide a separate release archive containing the files.
I don't believe there is a repository setting that makes the standard Download ZIP option automatically resolve LFS files. It would be useful if GitHub offered that as an option, especially for repositories where users are expected to download assets without installing Git LFS.