Git Large File Storage, an extension that keeps small pointer files in the repository while big binaries live elsewhere, and offers locking for files that cannot be diffed. Azure Repos supports it at no charge, but not over SSH.
Also called Git Large File Storage.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Git LFS in context, with comparison tables and the common traps.
Terms in this definition
- PTR
Turns an IP address back into a host name. These records live in reverse lookup zones.
- Repository
A group of images or artefacts in a container registry that share one name and differ by tag. Names can include slash-separated namespaces, but every repository is handled separately.
- Azure Repos
Azure DevOps' version control: Git (and legacy centralised TFVC), guarded by branch permissions and policies. GitHub's counterpart is its repositories.
- OVER
Gives a T-SQL window function its window: PARTITION BY, ORDER BY and, if wanted, a ROWS or RANGE frame. Rankings and running totals can then be worked out while every row is kept.
- SSH
Protocol for remote sessions, chiefly on Linux, using TCP port 22.
Related terms
- Pointer file
A tiny text file, made up of version, oid and size lines, that Git LFS commits instead of the real binary. Anyone cloning without the LFS client receives these placeholders rather than the actual files.
- Scalar
A Git tool that began at Microsoft and tunes clones of huge repositories for speed. It replaces VFS for Git, and Microsoft Learn points to it, Git LFS or Azure Artifacts when a repository grows too big.