If you switch branches, it will automatically check if you need a specific version of such a big file and get it for you - on demand. Instead, it only provides the files you actually need in your checked out revision. The LFS extension uses a simple technique to avoid your local Git repository from exploding like that: it does not keep all versions of a file on your machine. And, as already mentioned, most of this data will be of little value: usually, old versions of files aren't used on a daily basis - but they still weigh a lot of Megabytes. When a coworker clones that repository to her local machine, she will need to download a huge amount of data. After a couple of iterations, your local repository will quickly weigh tons of Megabytes and soon Gigabytes.
When you make a change to this file (no matter how tiny it might be), committing this modification will save the complete file (huge as it is) in your repository.
Let's say you have a 100 MB Photoshop file in your project.
An LFS-enhanced local Git repository will be significantly smaller in size because it breaks one basic rule of Git in an elegant way: it does not keep all of the project's data in your local repository. This problem in mind, Git's standard feature set was enhanced with the "Large File Storage" extension - in short: "Git LFS". Most annoyingly, the majority of this huge amount of data is probably useless for you: most of the time, you don't need each and every version of a file on your disk. Working with large binary files can be quite a hassle: they bloat your local repository and leave you with Gigabytes of data on your machine. Learn on: Desktop GUI | Command Line Language: EN Handling Large Files with LFS
0 kommentar(er)
