Merge branch 'jalen-limits-move' into 'master'

Moved limit file to admin folder(rate_limits move)

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/125614



Merged-by: Suzanne Selhorn <sselhorn@gitlab.com>
Co-authored-by: Jalen Hampton <jalen@Jalens-MacBook-Pro.local>

doc/administration/settings/git_lfs_rate_limits.md

+---
+stage: Create
+group: Source Code
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
+type: reference
+---
+
+# Rate limits on Git LFS **(FREE SELF)**
+
+[Git LFS (Large File Storage)](../../topics/git/lfs/index.md) is a Git extension
+for handling large files. If you use Git LFS in your repository, common Git operations
+can generate many Git LFS requests. You can enforce
+[general user and IP rate limits](../../user/admin_area/settings/user_and_ip_rate_limits.md), but you can also
+override the general setting to enforce additional limits on Git LFS requests. This
+override can improve the security and durability of your web application. Aside from
+precedence, this configuration provides the same features as the general user and IP
+rate limits.
+
+## Configure Git LFS rate limits
+
+Git LFS rate limits are disabled by default. If enabled and configured, these limits
+supersede the [general user and IP rate limits](../../user/admin_area/settings/user_and_ip_rate_limits.md):
+
+1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
+1. Select **Admin Area**.
+1. Select **Settings > Network**.
+1. Expand **Git LFS Rate Limits**.
+1. Select **Enable authenticated Git LFS request rate limit**.
+1. Enter a value for **Max authenticated Git LFS requests per period per user**.
+1. Enter a value for **Authenticated Git LFS rate limit period in seconds**.
+1. Select **Save changes**.
+
+## Related topics
+
+- [Rate limiting](../../security/rate_limits.md)
+- [User and IP rate limits](../../user/admin_area/settings/user_and_ip_rate_limits.md)

doc/user/admin_area/settings/git_lfs_rate_limits.md

 ---
-stage: Create
-group: Source Code
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
-type: reference
+redirect_to: '../../../administration/settings/git_lfs_rate_limits.md'
+remove_date: '2023-10-06'
 ---
 
-# Rate limits on Git LFS **(FREE SELF)**
+This document was moved to [another location](../../../administration/settings/git_lfs_rate_limits.md).
 
-[Git LFS (Large File Storage)](../../../topics/git/lfs/index.md) is a Git extension
-for handling large files. If you use Git LFS in your repository, common Git operations
-can generate many Git LFS requests. You can enforce
-[general user and IP rate limits](user_and_ip_rate_limits.md), but you can also
-override the general setting to enforce additional limits on Git LFS requests. This
-override can improve the security and durability of your web application. Aside from
-precedence, this configuration provides the same features as the general user and IP
-rate limits.
-
-## Configure Git LFS rate limits
-
-Git LFS rate limits are disabled by default. If enabled and configured, these limits
-supersede the [general user and IP rate limits](user_and_ip_rate_limits.md):
-
-1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
-1. Select **Admin Area**.
-1. Select **Settings > Network**.
-1. Expand **Git LFS Rate Limits**.
-1. Select **Enable authenticated Git LFS request rate limit**.
-1. Enter a value for **Max authenticated Git LFS requests per period per user**.
-1. Enter a value for **Authenticated Git LFS rate limit period in seconds**.
-1. Select **Save changes**.
-
-## Related topics
-
-- [Rate limiting](../../../security/rate_limits.md)
-- [User and IP rate limits](user_and_ip_rate_limits.md)
+<!-- This redirect file can be deleted after <2023-10-06>. -->
+<!-- Redirects that point to other docs in the same project expire in three months. -->
+<!-- Redirects that point to docs in a different project or site (for example, link is not relative and starts with `https:`) expire in one year. -->
+<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/redirects.html -->