/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 1 commit ahead, 2240 commits behind master.
Latest commit 8e201c3 Dec 8, 2016 @ttaylorr ttaylorr test: reproduce git-lfs/git-lfs#1726
Permalink
Failed to load latest commit information.
api fix import merge conflicts Nov 17, 2016
auth update other github/git-lfs references Nov 15, 2016
commands bring the checkout filter back Dec 7, 2016
config fix ssh endpoint parsing Dec 5, 2016
debian unused. Nov 22, 2016
docker run against gitlfs packages from docker hub Aug 2, 2016
docs remove deprecated features Nov 18, 2016
errors errors: remove Error prefix Aug 19, 2016
filepathfilter use internal channel methods, remove unused methods Nov 23, 2016
git git: parse filter process header values containing '=' properly Dec 2, 2016
httputil resolve master conflict Nov 15, 2016
lfs
localstorage fix problems running 'install' in a root dir Nov 30, 2016
progress Print report from meter when there were files but they were skipped Jun 8, 2016
rpm rpm: build Git LFS in the right directory Nov 17, 2016
script
subprocess Removed Go 1.6-specific API changes introduced in the previous commit… Jun 30, 2016
test test: reproduce git-lfs/git-lfs#1726 Dec 8, 2016
tools get rid of FileExists() check, check OpenFile() error instead Nov 29, 2016
transfer update package imports Nov 15, 2016
vendor/github.com unused. Nov 22, 2016
.gitattributes Enable autocrlf Aug 23, 2015
.gitignore Don't ignore source files named lfstest-*.go, only compiled binaries Jul 13, 2016
.mailmap Update .mailmap Oct 18, 2016
.travis.yml travis: build using Go v1.7.4 Dec 2, 2016
CHANGELOG.md release: 1.5.0 Nov 17, 2016
CODE-OF-CONDUCT.md embed the open code of conduct since the link is bad now May 6, 2016
CONTRIBUTING.md CONTRIBUTING: minimum Go is 1.7.3 Nov 23, 2016
INSTALLING.md update other github/git-lfs references Nov 15, 2016
LICENSE.md Add copyright date to license Nov 23, 2016
Makefile update other github/git-lfs references Nov 15, 2016
README.md Use new Travis CI URL Nov 26, 2016
ROADMAP.md
appveyor.yml appveyor: build using Go v1.7.4 Dec 2, 2016
circle.yml set path for custom git on each test run Nov 15, 2016
git-lfs.go update package imports Nov 15, 2016
glide.lock unused. Nov 22, 2016
glide.yaml unused. Nov 22, 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.5 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/git-lfs/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 | |---|---|---|---|---|---| | | | | | |