Configuring rate limits
You can set rate limits for GitHub Enterprise Server using the Management Console.
In this article
- Enabling rate limits for the GitHub Enterprise Server API
- Enabling abuse rate limits
- Enabling Git rate limits
Enabling rate limits for the GitHub Enterprise Server API
Enabling rate limits on the GitHub Enterprise Server API can prevent overuse of resources by individual or unauthenticated users. For more information, see "Rate Limiting" in the GitHub Developer documentation.
Note: The Management Console lists the time period (per minute or per hour) for each rate limit.
-
In the upper-right corner of any page, click .
-
In the left sidebar, click Management Console.
-
Under "Rate Limiting", select Enable API Rate Limiting.
-
Type limits for authenticated and unauthenticated requests for each API, or accept the pre-filled default limits.
-
Under the left sidebar, click Save settings.
Enabling abuse rate limits
Setting abuse rate limits protects the overall level of service on your GitHub Enterprise Server instance.
-
In the upper-right corner of any page, click .
-
In the left sidebar, click Management Console.
-
Under "Rate Limiting", select Enable Abuse Rate Limiting.
-
Type limits for Total Requests, CPU Limit, and CPU Limit for Searching, or accept the pre-filled default limits.
-
Under the left sidebar, click Save settings.
Enabling Git rate limits
You can apply Git rate limits per repository network or per user ID. Git rate limits are expressed in concurrent operations per minute, and are adaptive based on the current CPU load.
-
In the upper-right corner of any page, click .
-
In the left sidebar, click Management Console.
-
Under "Rate Limiting", select Enable Git Rate Limiting.
-
Type limits for each repository network or user ID.
-
Under the left sidebar, click Save settings.