You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
brian m. carlson 7237dd0fed
Merge pull request #3995 from dan2468/patch-1
4 days ago
.circleci circleci: remove blank lines from config 6 months ago
.github .github/workflows: temporarily fix path on Windows 1 week ago
commands Optimize pushes of multiple refs 1 week ago
config release: v2.10.0 6 days ago
creds creds: move Access types into creds package 1 month ago
debian release: v2.10.0 6 days ago
docker Add support for CentOS 8 3 months ago
docs docs/spec: document that pointer files are unique 1 month ago
errors Fix error strings to follow Go guidelines 3 months ago
filepathfilter filepathfilter: don't say file is both accepted and rejected 1 year ago
fs Fix error strings to follow Go guidelines 3 months ago
git install: don't print error if run outside repository 3 weeks ago
lfs Optimize pushes of multiple refs 1 week ago
lfsapi Add support for Kerberos authentication 1 month ago
lfshttp lfshttp: improve proxy support 2 weeks ago
locking Fix error strings to follow Go guidelines 3 months ago
rpm release: v2.10.0 6 days ago
script Include ppc64le and s390x Linux builds in releases 1 week ago
subprocess Drop pre-1.6 Go compatibility code 2 months ago
t Optimize pushes of multiple refs 1 week ago
tasklog tasklog/log.go: print "done" messages with a trailing period 5 months ago
tools tools: handle missing cygpath gracefully 2 months ago
tq creds: move Access types into creds package 1 month ago
vendor Vendor the Go httpproxy module 2 weeks ago
.gitattributes Enable autocrlf 4 years ago
.gitignore t: store test_count{,.lock} in t, not t/remote 1 year ago
.mailmap Add myself to .mailmap 2 years ago
.travis.yml Make Travis run tests on the proper version 5 months ago
CHANGELOG.md release: v2.10.0 6 days ago
CODE-OF-CONDUCT.md embed the open code of conduct since the link is bad now 3 years ago
CONTRIBUTING.md CONTRIBUTING: reflect the supported versions of Go 1 month ago
INSTALLING.md update other github/git-lfs references 3 years ago
LICENSE.md updated copyright year 5 days ago
Makefile Include ppc64le and s390x Linux builds in releases 1 week ago
README.md Add CI link to CI badge in README 1 month ago
appveyor.yml all: use Go 1.11.1 in CI 1 year ago
git-lfs.go Run go generate only on Windows 1 year ago
git-lfs_windows.go Run go generate only on Windows 1 year ago
go.mod go.mod: add SPNEGO modules 1 month ago
go.sum go.mod: add SPNEGO modules 1 month ago
versioninfo.json release: v2.10.0 6 days ago

README.md

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

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)`](https://github.com/git-lfs/git-lfs/blob/master/docs/man/git-lfs-migrate.1.ronn).

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

```bash
$ 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