diff options
author | Robert Schilling <rschilling@student.tugraz.at> | 2015-11-19 17:05:30 +0100 |
---|---|---|
committer | Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> | 2015-11-20 11:23:05 +0100 |
commit | 5ac2c3f0aa8730e0b874706965ce734a2318fa93 (patch) | |
tree | b8d142b2f4f75f5e4e85bae6e8372ce4d46c168a | |
parent | dc030ac1b4e6fc0329d5a464b14c2c24acc4f36f (diff) | |
download | gitlab-ce-5ac2c3f0aa8730e0b874706965ce734a2318fa93.tar.gz |
Update LFS docs for cloning [ci skip]
-rw-r--r-- | doc/workflow/git_lfs.md | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/workflow/git_lfs.md b/doc/workflow/git_lfs.md index e1064051fe8..616a71522ae 100644 --- a/doc/workflow/git_lfs.md +++ b/doc/workflow/git_lfs.md @@ -55,7 +55,7 @@ In `config/gitlab.yml`: * When SSH is set as a remote, Git LFS objects still go through HTTPS * Any Git LFS request will ask for HTTPS credentials to be provided so good Git credentials store is recommended * Currently, storing GitLab Git LFS objects on a non-local storage (like S3 buckets) is not supported -* Git LFS always assumes HTTPS so if you have GitLab server on HTTP you will have to add the url to Git config manually (see #troubleshooting-tips) +* Git LFS always assumes HTTPS so if you have GitLab server on HTTP you will have to add the URL to Git config manually (see #troubleshooting-tips) ## Using Git LFS @@ -77,11 +77,10 @@ git commit -am "Added Debian iso" # commit the file meta data git push origin master # sync the git repo and large file to the GitLab server ``` -Downloading a single large file is also very simple: +Cloning the repository works the same as before. Git automatically detects the LFS-tracked files and clones them via HTTP. If you performed the git clone command with a SSH URL, you have to enter your GitLab credentials for HTTP authentication. ```bash git clone git@gitlab.example.com:group/project.git -git lfs fetch debian.iso # download the large file ``` |