diff options
| author | Robert Schilling <rschilling@student.tugraz.at> | 2015-11-19 17:05:30 +0100 |
|---|---|---|
| committer | Robert Schilling <rschilling@student.tugraz.at> | 2015-11-19 17:05:30 +0100 |
| commit | 91a76957e3d18e3cb89bc8320f8513e1002e551e (patch) | |
| tree | 69fcf77b1c84fe3942210c6f81aa7b0815e01220 | |
| parent | 6756f87f90a6d8e80470ade835689f4d64bef35d (diff) | |
| download | gitlab-ce-update-lfs-docs.tar.gz | |
Update LFS docs for cloning [ci skip]update-lfs-docs
| -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 ``` |