/git-lfs

Git extension for versioning large files
  1. Go 72.2%
  2. Shell 27.1%
  3. Other 0.7%
Go Shell Other
Clone or download

Clone with HTTPS

Use Git or checkout with SVN using the web URL.

Download ZIP
Find file
Switch branches/tags
Nothing to show
Pull request Compare This branch is 41 commits ahead, 2621 commits behind master.
Latest commit 6b90c22 Oct 24, 2016 @sinbad sinbad Prove content of files is being updated at checkout even if readonly
Permalink
Failed to load latest commit information.
api api: use fmt.Fprintln to write to os.Stderr Oct 14, 2016
auth api,auth,errors,httputil,lfs,transfer: wrap errors Aug 18, 2016
commands Support `GIT_LFS_SET_LOCKABLE_READONLY` env var, can be disabled Oct 24, 2016
config Move reading of attributes files to config Oct 17, 2016
debian release: v1.4.2 Oct 10, 2016
docker run against gitlfs packages from docker hub Aug 2, 2016
docs Define interface on lfs track for locking Oct 17, 2016
errors Add post-checkout command which can fix lockable write flags Oct 17, 2016
git GetFilesChanged now supports getting files changed at a single commit… Oct 17, 2016
httputil Add HTTP 507 (Insufficient Storage) to the list of optional statuses (#… Aug 22, 2016
lfs Add post-commit hook which sets lockable files read-only Oct 17, 2016
localstorage vendor: vendor dependencies in vendor/ using Glide May 23, 2016
locking Support `GIT_LFS_SET_LOCKABLE_READONLY` env var, can be disabled Oct 24, 2016
progress Print report from meter when there were files but they were skipped Jun 8, 2016
rpm release: v1.4.2 Oct 10, 2016
script First pass at implementing lock cache using boltdb Oct 17, 2016
subprocess Removed Go 1.6-specific API changes introduced in the previous commit… Jun 30, 2016
test Prove content of files is being updated at checkout even if readonly Oct 24, 2016
tools Fix unit tests on Windows, chmod support on Windows is limited Oct 24, 2016
transfer errors: use github.com/pkg/errors instead of removed errutil package Aug 24, 2016
vendor/github.com Embed bolt in repo, forgot we did that even using glide Oct 18, 2016
.gitattributes Enable autocrlf Aug 23, 2015
.gitignore Don't ignore source files named lfstest-*.go, only compiled binaries Jul 13, 2016
.mailmap Add a .mailmap file Oct 13, 2016
.travis.yml travis: run tests on Go 1.7.1 Oct 10, 2016
CHANGELOG.md release: v1.4.2 Oct 10, 2016
CODE-OF-CONDUCT.md embed the open code of conduct since the link is bad now May 6, 2016
CONTRIBUTING.md Added branch name (master) to CONTRIBUTING.md Jul 28, 2016
INSTALLING.md small typos Apr 14, 2016
LICENSE.md Rename LICENSE to LICENSE.md Aug 4, 2015
Makefile Create Makefile for building with gccgo May 18, 2016
README.md README: add AppVeyor badge Oct 11, 2016
ROADMAP.md release: v1.4.2 Oct 10, 2016
appveyor.yml Enable running tests on AppVeyor CI Oct 10, 2016
git-lfs.go replace config.Config references in httputil Jul 22, 2016
glide.lock First pass at implementing lock cache using boltdb Oct 17, 2016
glide.yaml First pass at implementing lock cache using boltdb Oct 17, 2016

README.md

Git Large File Storage

Build Status 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 Git LFS website for an overview of features.

Getting Started

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

Note: Git LFS requires Git v1.8.2 or higher.

Once installed, you need to setup the global Git hooks for Git LFS. This only needs to be done once per machine.

$ git lfs install

Now, it's time to add some large files to a repository. The first step is to specify file patterns to store with Git LFS. These file patterns are stored in .gitattributes.

$ mkdir large-repo
$ cd large-repo
$ git init

# Add all zip files through Git LFS
$ git lfs track "*.zip"

Now you're ready to push some commits:

$ git add .gitattributes
$ git add my.zip
$ git commit -m "add zip"

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

$ git lfs ls-files
my.zip

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

$ git push origin master
Sending my.zip
LFS: 12.58 MB / 12.58 MB  100.00 %
Counting objects: 2, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 548 bytes | 0 bytes/s, done.
Total 5 (delta 1), reused 0 (delta 0)
To https://github.com/github/git-lfs-test
   67fcf6a..47b2002  master -> master

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 ask questions in the Git LFS chat room, or file a new issue. Be sure to include details about the problem so we can troubleshoot it.

  1. Include the output of git lfs env, which shows how your Git environment is setup.
  2. Include GIT_TRACE=1 in any bad Git commands to enable debug messages.
  3. If the output includes a message like Errors logged to /path/to/.git/lfs/objects/logs/*.log, throw the contents in the issue, or as a link to a Gist or paste site.

Contributing

See CONTRIBUTING.md for info on working on Git LFS and sending patches. Related projects are listed on the Implementations wiki page. You can also join the project's chat room.

Using LFS from other Go code

At the moment git-lfs is only focussed on the stability of its command line interface, and the server APIs. The contents of the source packages is subject to change. We therefore currently discourage other Go code from depending on the git-lfs packages directly; an API to be used by external Go code may be provided in future.

Core Team

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

In alphabetical order:

| @andyneff | @rubyist | @sinbad | @technoweenie | @ttaylorr | |---|---|---|---|---|---| | | | | | |