diff options
| author | Achilleas Pipinellis <axil@gitlab.com> | 2018-02-20 10:02:11 +0100 |
|---|---|---|
| committer | Achilleas Pipinellis <axil@gitlab.com> | 2018-02-20 10:03:07 +0100 |
| commit | fff70a04e1444d108ce02c0370ee85a0ecb07817 (patch) | |
| tree | 072e697b672359967cccb843097dc43333a02a3b | |
| parent | b44b4d4d649c6b48b537909932a8cd3606f472b7 (diff) | |
| download | gitlab-ce-docs/lfs-lock.tar.gz | |
Add version which LFS lock was introduceddocs/lfs-lock
| -rw-r--r-- | doc/workflow/lfs/manage_large_binaries_with_git_lfs.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/workflow/lfs/manage_large_binaries_with_git_lfs.md b/doc/workflow/lfs/manage_large_binaries_with_git_lfs.md index 8fff3d591fe..377eee69c11 100644 --- a/doc/workflow/lfs/manage_large_binaries_with_git_lfs.md +++ b/doc/workflow/lfs/manage_large_binaries_with_git_lfs.md @@ -34,7 +34,7 @@ Documentation for GitLab instance administrators is under [LFS administration do credentials store is recommended * 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](#troubleshooting)) - + >**Note**: With 8.12 GitLab added LFS support to SSH. The Git LFS communication still goes over HTTP, but now the SSH client passes the correct credentials to the Git LFS client, so no action is required by the user. @@ -85,6 +85,8 @@ git lfs fetch master ## File Locking +> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/35856) in GitLab 10.5. + The first thing to do before using File Locking is to tell Git LFS which kind of files are lockable. The following command will store PNG files in LFS and flag them as lockable: |