Diagram
A system architecture diagram showing how Git LFS stores small text pointers in Azure Repos while large binary file contents are stored on a remote LFS server, fetched lazily by the developer's local machine.
Git LFS and git-fat in Azure Repositories
Managing large files in a standard repository can slow down development because every clone downloads the full history of those assets. Git Large File Storage (Git LFS) addresses this issue by replacing large files in the repository with tiny text pointers while storing the actual data on a remote server. When a developer clones the repository, Git LFS only downloads these pointers and lazily fetches the full files when they are actually needed. This keeps local repositories small and ensures that common Git operations remain fast.
Domain 2 of 2
12 practice questions
Practice this DomainLast updated