Git Large File Storage

Git LFS is a command line extension andspecification for managing large files with Git.

The client is written in Go, with pre-compiled binaries available for Mac,Windows, Linux, and FreeBSD. Check out the websitefor an overview of features.

Getting Started

Downloading

You can install the Git LFS client in several different ways, depending on yoursetup and preferences.

• Linux users. Debian and RPM packages are available fromPackageCloud.
• macOS users. Homebrew bottles are distributed, and canbe installed via brew install git-lfs.
• Windows users. Git LFS is included in the distribution ofGit for Windows. Alternatively, you caninstall a recent version of Git LFS from the Chocolatey package manager.
• Binary packages. In addition, binary packages areavailable for Linux, macOS, Windows, and FreeBSD.
• Building from source. This repository can also bebuilt from source using the latest version of Go, and theavailable instructions in ourWiki.

Installing

From binary

The binary packages include a script which will:

• Install Git LFS binaries onto the system $PATH
• Run git lfs install toperform required global configuration changes.

$ ./install.sh

From source

• Place the git-lfs binary on your system’s executable $PATH or equivalent.
• Git LFS requires global configuration changes once per-machine. This can be done byrunning:

$ git lfs install

Verifying releases

Releases are signed with the OpenPGP key of one of the core team members. Toget these keys, you can run the following command, which will print them tostandard output:

$ curl -L https://api.github.com/repos/git-lfs/git-lfs/tarball/core-gpg-keys | tar -Ozxf -

Once you have the keys, you can download the sha256sums.asc file and verifythe file you want like so:

$ gpg -d sha256sums.asc | grep git-lfs-linux-amd64-v2.10.0.tar.gz | shasum -a 256 -c

Example Usage

To begin using Git LFS within a Git repository that is not already configuredfor Git LFS, you can indicate which files you would like Git LFS to manage.This can be done by running the following from within a Git repository:

$ git lfs track "*.psd"

(Where *.psd is the pattern of filenames that you wish to track. You can readmore about this pattern syntaxhere).

Note: the quotation marks surrounding the pattern are important toprevent the glob pattern from being expanded by the shell.

After any invocation of git-lfs-track(1) or git-lfs-untrack(1), you mustcommit changes to your .gitattributes file. This can be done by running:

$ git add .gitattributes$ git commit -m "track *.psd files using Git LFS"

You can now interact with your Git repository as usual, and Git LFS will takecare of managing your large files. For example, changing a file named my.psd(tracked above via *.psd):

$ git add my.psd$ git commit -m "add psd"

Tip: if you have large files already in your repository's history, git lfs track will not track them retroactively. To migrate existing large filesin your history to use Git LFS, use git lfs migrate. For example:

$ git lfs migrate import --include="*.psd" --everything

For more information, read git-lfs-migrate(1).

You can confirm that Git LFS is managing your PSD file:

$ git lfs ls-files3c2f7aedfb * my.psd

Once you've made your commits, push your files to the Git remote:

$ git push origin masterUploading LFS objects: 100% (1/1), 810 B, 1.2 KB/s# ...To https://github.com/git-lfs/git-lfs-test   67fcf6a..47b2002  master -> master

Note: Git LFS requires at least Git 1.8.2 on Linux or 1.8.5 on macOS.

Limitations

Git LFS maintains a list of currently known limitations, which you can find andedit here.

Need Help?

You can get help on specific commands directly:

$ git lfs help <subcommand>

The official documentation has command references and specifications forthe tool.

You can always open an issue, andone of the Core Team members will respond to you. Please be sure to include:

1. The output of git lfs env, which displays helpful information about yourGit repository useful in debugging.
2. Any failed commands re-run with GIT_TRACE=1 in the environment, whichdisplays additional information pertaining to why a command crashed.

Contributing

See CONTRIBUTING.md for info on working on Git LFS andsending patches. Related projects are listed on the Implementations wikipage.

Core Team

These are the humans that form the Git LFS core team, which runs the project.

In alphabetical order:

@bk2204	@chrisd8088	@larsxschneider

Alumni

These are the humans that have in the past formed the Git LFS core team, orhave otherwise contributed a significant amount to the project. Git LFS wouldnot be possible without them.

In alphabetical order:

@andyneff	@PastelMobileSuit	@rubyist	@sinbad	@technoweenie	@ttaylorr