kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Update diff_limits.md

Browse source
This commit is contained in:
Russell Dickenson 2019-05-30 06:49:38 +00:00 committed by Achilleas Pipinellis
parent 2d4df0aaf8
commit 0daa8c12e7
1 changed files with 30 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

41
doc/user/admin_area/diff_limits.md
View file

@ -1,21 +1,40 @@
---
type: reference
---
# Diff limits administration
You can set a maximum size for display of diff files (patches).
## Maximum diff patch size
Diff files which exceed this value will be presented as 'too large' and won't
be expandable. Instead of an expandable view, a link to the blob view will be
shown.
Patches greater than 10% of this size will be automatically collapsed, and a
link to expand the diff will be presented.
NOTE: **Note:**
Merge requests and branch comparison views will be affected.
CAUTION: **Caution:**
These settings are currently under experimental state. They'll
increase the resource consumption of your instance and should
be edited mindfully.
This setting is experimental. An increased maximum will increase resource
consumption of your instance. Keep this in mind when adjusting the maximum.
1. Access **Admin area > Settings > General**
1. Expand **Diff limits**
1. Go to **Admin area > Settings > General**.
1. Expand **Diff limits**.
1. Enter a value for **Maximum diff patch size**, measured in bytes.
1. Click on **Save changes**.
### Maximum diff patch size
<!-- ## Troubleshooting
This is the content size each diff file (patch) is allowed to reach before
it's collapsed, without the possibility of being expanded. A link redirecting
to the blob view will be presented for the patches that surpass this limit.
Include any troubleshooting steps that you can foresee. If you know beforehand what issues
one might have when setting this up, or when something is changed, or on upgrading, it's
important to describe those, too. Think of things that may go wrong and include them here.
This is important to minimize requests for support, and to avoid doc comments with
questions that you know someone might ask.
Patches surpassing 10% of this content size will be automatically collapsed,
but expandable (a link to expand the diff will be presented).
Each scenario can be a third-level heading, e.g. `### Getting error message X`.
If you have none to add when creating a doc, leave this section in place
but commented out to help encourage others to add to it in the future. -->