diff options
| author | Marcel Amirault <mamirault@gitlab.com> | 2019-07-15 03:46:34 +0300 |
|---|---|---|
| committer | Evan Read <eread@gitlab.com> | 2019-07-15 03:46:34 +0300 |
| commit | 3ee846c9dbd63cba09706cb2b5e1dd760b46fcc8 (patch) | |
| tree | 6c6dbf17fe3c0b5a19dfedc6c2339c3075acee0a /doc/workflow | |
| parent | 5f6c98e0c384ce50c279bb07c9546c7807cb8bc8 (diff) | |
Remove trailing whitespace in docs
Remove unneeded trailing whitespace in lines in
/security /workflow /user docs
Diffstat (limited to 'doc/workflow')
| -rw-r--r-- | doc/workflow/issue_weight.md | 2 | ||||
| -rw-r--r-- | doc/workflow/lfs/manage_large_binaries_with_git_lfs.md | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/doc/workflow/issue_weight.md b/doc/workflow/issue_weight.md index afb623e1967..a80519f0748 100644 --- a/doc/workflow/issue_weight.md +++ b/doc/workflow/issue_weight.md @@ -9,7 +9,7 @@ value or complexity a given issue has or will cost. You can set the weight of an issue during its creation, by simply changing the value in the dropdown menu. You can set it to a non-negative integer -value from 0, 1, 2, and so on. (The database stores a 4-byte value, so the +value from 0, 1, 2, and so on. (The database stores a 4-byte value, so the upper bound is essentially limitless). You can remove weight from an issue as well. 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 202f2e39975..b6bba57049d 100644 --- a/doc/workflow/lfs/manage_large_binaries_with_git_lfs.md +++ b/doc/workflow/lfs/manage_large_binaries_with_git_lfs.md @@ -250,7 +250,7 @@ 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, +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. 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). |