diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-04-08 09:09:54 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-04-08 09:09:54 +0300 |
| commit | f6cdec670b9b757fc2225a2c6627ab79765e5b8a (patch) | |
| tree | 7a1fde030f117b69332d01b22deefd1c81fff458 /doc/development/merge_request_performance_guidelines.md | |
| parent | e2ee1eec50aa8df8543d7ecc585ec0ba5ee544ac (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/merge_request_performance_guidelines.md')
| -rw-r--r-- | doc/development/merge_request_performance_guidelines.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/merge_request_performance_guidelines.md b/doc/development/merge_request_performance_guidelines.md index a285d30d7a5..4a9b5d26aef 100644 --- a/doc/development/merge_request_performance_guidelines.md +++ b/doc/development/merge_request_performance_guidelines.md @@ -375,7 +375,7 @@ Examples: In such cases it's rather expected that this is either misuse or abuse of the feature. Lack of the upper limit can result in service degradation as the system will try to process all schedules - assigned the the project. + assigned the project. 1. GitLab CI/CD includes: We started with the limit of maximum of 50 nested includes. We understood that performance of the feature was acceptable at that level. |