diff options
| author | Lee Matos <lee@gitlab.com> | 2019-04-04 17:06:52 +0000 |
|---|---|---|
| committer | Lee Matos <lee@gitlab.com> | 2019-04-04 17:06:52 +0000 |
| commit | 94a3b47384536e670975b61b089770cd505acde9 (patch) | |
| tree | ccdad4865b69c73414f8c50d13c95d84c9d5624e | |
| parent | 9ac2e39800db15336d4c9b68157f046da678769b (diff) | |
| download | gitlab-ce-patch-44.tar.gz | |
Apply suggestion to doc/workflow/lfs/manage_large_binaries_with_git_lfs.mdpatch-44
| -rw-r--r-- | doc/workflow/lfs/manage_large_binaries_with_git_lfs.md | 2 |
1 files changed, 1 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 f484db1afdf..202f2e39975 100644 --- a/doc/workflow/lfs/manage_large_binaries_with_git_lfs.md +++ b/doc/workflow/lfs/manage_large_binaries_with_git_lfs.md @@ -251,6 +251,6 @@ If you are storing LFS files outside of GitLab you can disable LFS on the projec It is possible to host LFS objects externally by setting a custom LFS url with `git config -f .lfsconfig lfs.url https://example.com/<project>.git/info/lfs`. You might choose to do this if you are using an appliance like a Sonatype Nexus to store LFS data. If you choose to use an external LFS store, -Gitlab will not be able to verify LFS objects which means that pushes will fail if you have GitLab LFS support enabled. +GitLab will not be able to verify LFS objects which means that pushes will fail if you have GitLab LFS support enabled. To stop push failure, LFS support can be disabled in the [Project settings](../../user/project/settings/index.md). This means you will lose GitLab LFS value-adds (Verifying LFS objects, UI integration for LFS). |