Vetrix Docs

Rate limits

The rate-limits page sets request budgets that apply only to this repository. Vetrix meters incoming traffic in named scopes (for example clones, pushes, or registry traffic), and each caller is normally held to a group-default budget for every scope. On this page you can add a per-repository override that raises or lowers the budget for one scope on this repository, see how often each scope was throttled recently, and remove an override to fall back to the group default. Managing overrides requires administrator access to the repository; without it, the page shows a message that you need the repository's rate-limit permission instead of the table.

Where to find it

  • URL: gitvetrix.com/<owner>/<repo>/settings/rate-limits
  • Navigation: open a repository, go to Settings, and in the settings sidebar select Rate limits.

The heading reads Rate limits for <owner>/<repo>.

Read the overrides table

The table has one row per scope, with these columns:

  • Scope — the traffic scope, with a short description of what it covers. The scopes are api.read (read-only API calls), api.write (API writes such as creating issues or editing settings), api.expensive (heavy API calls such as code search and analytics), git.read (clones, fetches, and ref lookups), git.write (pushes), registry (package and container registry traffic), and beacon (lightweight usage telemetry from the interface).
  • Override — the override budget for this repository, shown as the allowed requests per window and the burst allowance, together with the override's action. A scope with no override shows (group default), and an override that has been turned off shows disabled.
  • Throttled (24 h) — how many requests in that scope were throttled on this repository in the last 24 hours.
  • Controls — a Remove action on any scope that has an override.

Add a scope override

  1. Select Add scope override.
  2. In Scope, choose the scope the override applies to. A short description of the selected scope appears below the field.
  3. Set Requests per window (the number of allowed requests), Window seconds (the length of the window), and Burst (extra requests allowed above the steady rate).
  4. In Action, choose what happens when the budget is exceeded: allow (metered, never blocked), throttle (429 + Retry-After), or shadow (log-only).
  5. Leave Enabled selected to enforce the override, or clear it to keep the override defined but inactive.
  6. In Reason, enter why the override exists. A reason is required and is kept for the audit trail.
  7. Select Create override. The new override appears in the table row for that scope.

Select Cancel to close the form without saving.

Remove an override

  1. Find the scope in the table and select Remove in its Controls column.
  2. Confirm in the Remove override? dialog. The override is deleted and callers in that scope fall back to the group-default budget.

Request a wider change or review activity

Below the table:

  • When the instance administrator has published a contact address, a Request a change from the administrator link opens a pre-filled message for asking about an instance-wide rate-limit change.
  • A View throttled events link opens this repository's throttled-request activity.
  • Mirrors — configure pull and push mirrors for this repository.
  • Repository home — the repository landing page and its clone URLs.