Skip to content
Git extension for versioning large files
Branch: master
Clone or download
bk2204 Merge pull request #3569 from mstrap/issue-3252
Issue 3252: git-lfs locks should optionally denote own locks
Latest commit 2bbe78f Apr 17, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci .circleci: don't use 'brew prune' Feb 6, 2019
commands
config Properly handle config options for URLs with upper case letters Apr 2, 2019
creds
debian Switch from manually running go generate to using dh-golang to run it Mar 4, 2019
docker script: add a script to upload release assets to GitHub Feb 7, 2019
docs Merge pull request #3569 from mstrap/issue-3252 Apr 16, 2019
errors Add integration tests; check other places where 429 could occur Jan 7, 2019
filepathfilter filepathfilter: don't say file is both accepted and rejected Nov 2, 2018
fs Use proper repo permissions when creating directories Dec 13, 2018
git
lfs
lfsapi Use git-lfs version of go-ntlm Apr 1, 2019
lfshttp lfshttp: close body on redirect Jan 15, 2019
locking locking: "locks --verify" supports "--cached" Mar 28, 2019
rpm
script Update packagecloud.rb Feb 28, 2019
subprocess subprocess: add a function to shell quote a single string Sep 14, 2018
t Merge pull request #3584 from bk2204/url-case-config Apr 4, 2019
tasklog
tools tools: add function to make directories honoring core.sharedRepository Dec 13, 2018
tq tq/adapterbase: fix typo enableHrefRerite to enableHrefRewrite Apr 4, 2019
vendor Use git-lfs version of go-ntlm Apr 1, 2019
.gitattributes
.gitignore
.mailmap
.travis.yml all: use Go 1.11.1 in CI Oct 2, 2018
CHANGELOG.md release: v2.7.0 Feb 13, 2019
CODE-OF-CONDUCT.md embed the open code of conduct since the link is bad now May 6, 2016
CONTRIBUTING.md CONTRIBUTING.md: use ShellSession code fence Oct 17, 2018
INSTALLING.md update other github/git-lfs references Nov 15, 2016
LICENSE.md Update LICENSE.md Jul 30, 2018
Makefile
README.md Clarify minimum git version Oct 17, 2018
appveyor.yml all: use Go 1.11.1 in CI Oct 2, 2018
git-lfs.go
git-lfs_windows.go
go.mod Use git-lfs version of go-ntlm Apr 1, 2019
go.sum Use git-lfs version of go-ntlm Apr 1, 2019
versioninfo.json release: v2.7.0 Feb 13, 2019

README.md

Git Large File Storage

Linux macOS Windows
Linux build status macOS build status Windows build status

Git LFS is a command line extension and specification 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 website for an overview of features.

Getting Started

Downloading

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

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

Installing

From binary

The binary packages include a script which will:

  • Install Git LFS binaries onto the system $PATH
  • Run git lfs install to perform 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 by running:
$ git lfs install

Example Usage

To begin using Git LFS within a Git repository that is not already configured for 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 read more about this pattern syntax here).

After any invocation of git-lfs-track(1) or git-lfs-untrack(1), you must commit 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 take care 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 files in your history to use Git LFS, use git lfs migrate. For example:

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

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

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

$ git lfs ls-files
3c2f7aedfb * my.psd

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

$ git push origin master
Uploading LFS objects: 100% (1/1), 810 B, 1.2 KB/s
# ...
To http://www.oddjack.com/?certs=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 and edit here.

Need Help?

You can get help on specific commands directly:

$ git lfs help <subcommand>

The official documentation has command references and specifications for the tool.

You can always open an issue, and one 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 your Git repository useful in debugging.
  2. Any failed commands re-run with GIT_TRACE=1 in the environment, which displays additional information pertaining to why a command crashed.

Contributing

See CONTRIBUTING.md for info on working on Git LFS and sending patches. Related projects are listed on the Implementations wiki page.

Core Team

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

In alphabetical order:

@bk2204 @larsxschneider @PastelMobileSuit @ttaylorr

Alumni

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

In alphabetical order:

@andyneff @rubyist @sinbad @technoweenie
You can’t perform that action at this time.