LFS ‐ Large File Storage ‐ Best Practices - jrcloudsolutions/tidbits GitHub Wiki

Git is a technology of its own and outside GitLab, Github, Bitbucket, etc.

LFS binaries or blobs are .zip, .tar.gz, .iso, .pdf, .jpg, etc.

Code repos are strictly designed to store source code i.e. python, ruby, C++, etc.

1. LFS is compatible with GitLab, however this does not mean that GitLab will automatically track or flag binaries or blobs automatically. Binaries/blobs need to be manually tracked with git lfs.

2. LFS reference pointers in the code repo that point to the actual binaries or blobs will only show if the code repo was lfs tracked at the first commit from the get-go. If the binaries were LFS tracked after the first commit then it will only duplicate the binaries in LFS and keep the original binaries in the repo.

3. The GitLab UI does not provide a capability or feature to list LFS objects individually, it can only provide overall LFS storage by selecting Usage Quotas.

4. The only way to convert binaries or blobs to LFS after the first commit is to delete the .git folder, do a git lfs track, do a "git push origin master" to a brand new project.