brian m. carlson
Merge pull request #4259 from bk2204/socks5h
lfshttp: add support for socks5h proxies
|4 days ago|
|.circleci||1 year ago|
|.github||3 weeks ago|
|commands||3 weeks ago|
|config||3 weeks ago|
|creds||9 months ago|
|debian||3 weeks ago|
|docker||5 months ago|
|docs||1 month ago|
|errors||11 months ago|
|filepathfilter||3 months ago|
|fs||1 month ago|
|git||1 month ago|
|lfs||1 month ago|
|lfsapi||5 months ago|
|lfshttp||4 days ago|
|locking||3 months ago|
|rpm||3 weeks ago|
|script||5 days ago|
|subprocess||2 months ago|
|t||2 weeks ago|
|tasklog||1 year ago|
|tools||4 days ago|
|tq||5 months ago|
|vendor||4 days ago|
|.gitattributes||5 years ago|
|.gitignore||2 years ago|
|.mailmap||3 years ago|
|.travis.yml||1 year ago|
|CHANGELOG.md||3 weeks ago|
|CODE-OF-CONDUCT.md||4 years ago|
|CONTRIBUTING.md||1 week ago|
|INSTALLING.md||3 years ago|
|LICENSE.md||8 months ago|
|Makefile||3 weeks ago|
|README.md||1 week ago|
|SECURITY.md||2 weeks ago|
|appveyor.yml||2 years ago|
|git-lfs.go||1 year ago|
|git-lfs_windows.go||1 year ago|
|go.mod||4 days ago|
|go.sum||4 days ago|
|versioninfo.json||3 weeks ago|
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.
You can install the Git LFS client in several different ways, depending on your setup and preferences.
brew install git-lfs.
The binary packages include a script which will:
git lfs installto perform required global configuration changes.
git-lfsbinary on your system’s executable
$ git lfs install
Releases are signed with the OpenPGP key of one of the core team members. To get these keys, you can run the following command, which will print them to standard output:
$ curl -L https://api.github.com/repos/git-lfs/git-lfs/tarball/core-gpg-keys | tar -Ozxf -
Once you have the keys, you can download the
sha256sums.asc file and verify
the file you want like so:
$ gpg -d sha256sums.asc | grep git-lfs-linux-amd64-v2.10.0.tar.gz | shasum -a 256 -c
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"
*.psd is the pattern of filenames that you wish to track. You can read
more about this pattern syntax
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-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
(tracked above via
$ git add my.psd $ git commit -m "add psd"
Tip: if you have large files already in your repository’s history,
git lfs trackwill 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.
Git LFS maintains a list of currently known limitations, which you can find and edit here.
You can get help on specific commands directly:
$ git lfs help <subcommand>
You can always open an issue, and one of the Core Team members will respond to you. Please be sure to include:
git lfs env, which displays helpful information about your Git repository useful in debugging.
GIT_TRACE=1in the environment, which displays additional information pertaining to why a command crashed.
See also SECURITY.md for info on how to submit reports of security vulnerabilities.
These are the humans that form the Git LFS core team, which runs the project.
In alphabetical order:
|PGP 0223B187||PGP 088335A9||PGP A5795889|
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: