From 1a129420d6bd3e5223e8ba4a5b7749764118a885 Mon Sep 17 00:00:00 2001 From: GitLab Bot Date: Fri, 15 Jul 2022 12:10:10 +0000 Subject: Add latest changes from gitlab-org/gitlab@master --- doc/development/application_limits.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) (limited to 'doc/development/application_limits.md') diff --git a/doc/development/application_limits.md b/doc/development/application_limits.md index 6c7213ab235..2826b8a3bc4 100644 --- a/doc/development/application_limits.md +++ b/doc/development/application_limits.md @@ -12,8 +12,7 @@ limits to GitLab. ## Documentation First of all, you have to gather information and decide which are the different -limits that are set for the different GitLab tiers. You also need to -coordinate with others to [document](../administration/instance_limits.md) +limits that are set for the different GitLab tiers. Coordinate with others to [document](../administration/instance_limits.md) and communicate those limits. There is a guide about [introducing application @@ -206,6 +205,6 @@ rate limiting architecture: 1. Making it possible to define and override limits per namespace / per plan. 1. Automatically generating documentation about what limits are implemented and what the defaults are. -1. Defining limits in a single place that is easy to find an explore. +1. Defining limits in a single place that can be found and explored. 1. Soft and hard limits, with support for notifying users when a limit is approaching. -- cgit v1.2.3