正式なドキュメントは英語版であり、この日本語訳はAI支援翻訳により作成された参考用のものです。日本語訳の一部の内容は人間によるレビューがまだ行われていないため、翻訳のタイミングにより英語版との間に差異が生じることがあります。最新かつ正確な情報については、英語版をご参照ください。
ドキュメントに関する現在のご利用体験についてお聞かせください。アンケートにご協力ください。

Content creation rate limits

  • Tier: Free, Premium, Ultimate
  • Offering: GitLab Self-Managed

Rate limits control the pace at which users can create issues, epics, and notes.

Issue and epic creation

The limit for epic creation is the same limit applied to issue creation.

Prerequisites:

  • Administrator access.

To limit the number of requests made to the issue and epic creation endpoints:

  1. In the upper-right corner, select Admin.
  2. In the left sidebar, select Settings > Network.
  3. Expand Issues Rate Limits.
  4. Under Max requests per minute, enter the new value.
  5. Select Save changes.

The rate limit:

  • Is applied independently per project and per user.
  • Is not applied per IP address.
  • Is disabled by default.
  • Can be set to 0 to disable the rate limit.

Requests over the rate limit are logged into the auth.log file.

For example, if you set the limit to 300, requests that exceed a rate of 300 per minute are blocked. Access to the endpoint is available after one minute.

Note creation

You can configure the rate limit for requests to the note creation endpoint.

Prerequisites:

  • Administrator access.

To change the note creation rate limit:

  1. In the upper-right corner, select Admin.
  2. In the left sidebar, select Settings > Network.
  3. Expand Notes rate limit.
  4. In the Maximum requests per minute box, enter the new value.
  5. Optional. In the Users to exclude from the rate limit box, list users allowed to exceed the limit.
  6. Select Save changes.

The rate limit:

  • Is applied independently per user.
  • Is not applied per IP address.
  • Defaults to 300.

Requests over the rate limit are logged into the auth.log file.

For example, if you set the limit to 300, requests that exceed a rate of 300 per minute are blocked. Access to the endpoint is available after one minute.