Go to file
brian m. carlson f68ce7517b
install: don't print error if run outside repository
As of 2.9.2, if run outside of a repository, Git LFS will produce an
error if `git lfs install` is run outside of a repository.  This occurs
because we look for a specific string in the error message to detect if
the directory is not a repository, but that message was no longer
included since the standard output of `git rev-parse` is not included.

Include the standard error output in the message so that we correctly
detect whether the directory is a repository or not and avoid printing
an error message in this case if it is not.
2020-01-03 15:55:26 +00:00
.circleci circleci: remove blank lines from config 2019-07-11 23:10:05 +00:00
.github Merge pull request #3903 from bk2204/allow-windows-latest-git 2019-12-12 18:24:55 +00:00
commands Clarify output shown by git lfs status 2019-12-15 21:59:53 -08:00
config Interpret relative hook paths as relative to working tree 2019-11-21 17:19:55 +00:00
creds creds: move Access types into creds package 2019-12-09 15:35:52 +00:00
debian debian: bump version of golang-go 2019-12-19 20:00:56 +00:00
docker Add support for CentOS 8 2019-10-09 20:05:32 +00:00
docs docs/spec: document that pointer files are unique 2019-12-09 22:08:19 +00:00
errors Fix error strings to follow Go guidelines 2019-10-22 17:33:49 +03:00
filepathfilter filepathfilter: don't say file is both accepted and rejected 2018-11-02 18:40:15 +00:00
fs Fix error strings to follow Go guidelines 2019-10-22 17:33:49 +03:00
git install: don't print error if run outside repository 2020-01-03 15:55:26 +00:00
lfs status: update index before showing status 2019-11-18 20:37:52 +00:00
lfsapi Add support for Kerberos authentication 2019-12-09 15:35:53 +00:00
lfshttp Merge pull request #3941 from bk2204/kerberos 2020-01-03 14:51:47 +00:00
locking Fix error strings to follow Go guidelines 2019-10-22 17:33:49 +03:00
rpm rpm: use old setup code on CentOS 7 2019-12-02 16:09:46 +00:00
script script/packagecloud.rb: add shebang 2019-11-26 14:47:19 +00:00
subprocess Drop pre-1.6 Go compatibility code 2019-10-31 12:18:22 +03:00
t install: don't print error if run outside repository 2020-01-03 15:55:26 +00:00
tasklog tasklog/log.go: print "done" messages with a trailing period 2019-08-23 17:04:37 -04:00
tools tools: handle missing cygpath gracefully 2019-11-25 16:11:54 +00:00
tq creds: move Access types into creds package 2019-12-09 15:35:52 +00:00
vendor go.mod: add SPNEGO modules 2019-12-09 15:35:53 +00:00
.gitattributes Enable autocrlf 2015-08-22 21:03:44 -04:00
.gitignore t: store test_count{,.lock} in t, not t/remote 2018-07-11 13:58:02 -05:00
.mailmap Add myself to .mailmap 2017-02-24 21:10:42 +01:00
.travis.yml Make Travis run tests on the proper version 2019-08-05 21:24:24 +00:00
appveyor.yml all: use Go 1.11.1 in CI 2018-10-02 15:55:19 -07:00
CHANGELOG.md release: v2.9.0 2019-10-15 20:56:43 +00: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 CONTRIBUTING: reflect the supported versions of Go 2019-12-11 18:17:27 +00:00
git-lfs_windows.go Run go generate only on Windows 2019-01-15 22:17:53 +00:00
git-lfs.go Run go generate only on Windows 2019-01-15 22:17:53 +00:00
go.mod go.mod: add SPNEGO modules 2019-12-09 15:35:53 +00:00
go.sum go.mod: add SPNEGO modules 2019-12-09 15:35:53 +00:00
INSTALLING.md update other github/git-lfs references 2016-11-15 10:07:11 -07:00
LICENSE.md Update LICENSE.md 2018-07-30 21:17:02 +08:00
Makefile Makefile: make gzipped tarball really gzipped 2019-10-01 14:29:34 +00:00
README.md Add CI link to CI badge in README 2019-12-20 09:57:05 +03:00
versioninfo.json release: v2.9.0 2019-10-15 20:56:43 +00:00

Git Large File Storage

CI 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 systems 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).

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

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" --everything

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

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 @PastelMobileSuit @rubyist @sinbad @technoweenie @ttaylorr