Go to file
2018-07-19 13:15:52 -05:00
.circleci .circleci/config.yml: use installed Git 2018-03-20 18:30:17 -04:00
commands commands/command_migrate.go: instantiate filter in --fixup 2018-07-09 12:20:43 -05:00
config config/config.go: case-insensitive error search 2018-07-02 13:05:45 -05:00
debian Makefile: replace script/test with phony 'test' target 2018-07-16 16:25:54 -05:00
docker docker: add debian_9 image to default images list 2017-05-08 09:55:46 -06:00
docs Merge pull request #3114 from git-lfs/ttaylorr/migrate-fixup 2018-07-09 14:26:28 -05:00
errors Fix parentOf function to work with updated github.com/pkg/errors 2017-07-18 01:03:29 +00:00
filepathfilter filepathfilter: test correct set of global wildcards 2018-02-27 16:38:08 -08:00
fs add unittests 2018-06-27 00:57:05 +02:00
git git/githistory/rewriter_test.go: ensure calls over subtrees 2018-07-09 12:14:34 -05:00
lfs commands: use gitscanner for export 2018-07-03 11:13:25 -07:00
lfsapi Merge pull request #2934 from stanhu/sh-add-ssh-retries 2018-07-06 15:21:06 -05:00
locking locking: update schemas correctly 2017-12-14 16:27:25 -05:00
rpm Makefile: replace script/bootstrap with 'make', 'make all' 2018-07-19 13:14:39 -05:00
script script: remove unused script/update-version 2018-07-19 13:15:52 -05:00
subprocess git: run 'config' from dir based on *Configuration 2017-10-25 19:46:36 -06:00
tasklog tasklog: note alignemnt issue in *PercentageTask 2018-02-26 17:06:10 -08:00
test Makefile: replace script/bootstrap with 'make', 'make all' 2018-07-19 13:14:39 -05:00
tools tools/filetools: only handle non-Windows paths 2018-02-15 15:50:21 -08:00
tq tq/transfer.go: add Checkout direction 2018-06-08 15:47:52 -05:00
vendor/github.com vendor: update github.com/git-lfs/wildmatch 2018-07-06 14:42:48 -05:00
.gitattributes Enable autocrlf 2015-08-22 21:03:44 -04:00
.gitignore Update gitignore to add some temp files that get created when building debs 2017-07-17 19:55:12 +00:00
.mailmap Add myself to .mailmap 2017-02-24 21:10:42 +01:00
.travis.yml ci: disable integration tests on 'next' branch of git 2017-08-24 18:35:54 -04:00
appveyor.yml Makefile: replace script/bootstrap with 'make', 'make all' 2018-07-19 13:14:39 -05:00
CHANGELOG.md release: v2.4.0 2018-03-01 15:53:52 -08:00
CODE-OF-CONDUCT.md embed the open code of conduct since the link is bad now 2016-05-06 05:50:14 -06:00
CONTRIBUTING.md Makefile: replace script/bootstrap with 'make', 'make all' 2018-07-19 13:14:39 -05:00
git-lfs.go commands/run.go: teach Run() to return an exit code 2018-04-12 12:16:07 -07:00
glide.lock vendor: update github.com/git-lfs/wildmatch 2018-07-06 14:42:48 -05:00
glide.yaml vendor: update github.com/git-lfs/wildmatch 2018-07-06 14:42:48 -05:00
INSTALLING.md update other github/git-lfs references 2016-11-15 10:07:11 -07:00
LICENSE.md Add copyright date to license 2016-11-23 12:23:13 -05:00
Makefile Makefile: use SOURCES, not PKGS 2018-07-19 13:14:39 -05:00
README.md README.md: add link to installation wiki page 2018-06-18 18:52:36 -05:00
ROADMAP.md update other github/git-lfs references 2016-11-15 10:07:11 -07:00
versioninfo.json release: v2.4.0 2018-03-01 15:53:52 -08:00

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

Installation

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. Chocolatey packages are distributed, and can be installed via choco install git-lfs.

In addition, binary packages are available for Linux, macOS, Windows, and FreeBSD. This repository can also be built from source using the latest version of Go, and the available instructions in our Wiki.

Usage

Git LFS requires a global installation once per-machine. This can be done by running:

$ git lfs install

To begin using Git LFS within your Git repository, you can indicate which files you would like Git LFS to manage. This can be done by running the following from within 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 https://github.com/git-lfs/git-lfs-test
   67fcf6a..47b2002  master -> master

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

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:

@larsxschneider @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