Skip to content
RuleRoster

Source-backed platform rule

GitHub repository pull request merge rate limit

See the direct answer, scope, qualifiers, and current official evidence for GitHub repository pull request merge rate limit.

RuleRoster is independent and is not affiliated with or endorsed by GitHub.

Direct answer

What is the rule?

GitHub recommends no more than 1 merged pull request per minute; the source does not state a separate scope basis.

Scope
GitHub.com pull request activity
Rule verified
September 23, 2026

Published evidence

Rule details

Recommended limit

Recommended maximum: 1 merged pull request per minute. The source does not state a separate per-branch, repository, organization, or account basis. Higher merge activity can cause mergeability-check performance bottlenecks and a race-to-merge situation; these are possible effects, not guaranteed enforcement. When using a merge queue, GitHub suggests disabling "require this branch to be up to date before merging."

Applicability

Service: GitHub.com. Plans: Enterprise Cloud, Free, Pro, Team. Country: not stated. Device: not stated. Account class: not stated. Policy version: not stated.

Evidence trail

Official sources

Attribution and license

Source content: GitHub Docs by GitHub, licensed under CC BY 4.0: https://github.com/github/docs/blob/0a4d351cc1ff7134764f874808fb6829afbb73dd/LICENSE. Summarized and adapted by RuleRoster; verified 2026-09-23. No endorsement by GitHub is implied.

Interpretation and accountability

Before you act

  1. Confirm that the scope matches your case.
  2. Keep recommendations, enforced limits, exceptions, and unstated details distinct.
  3. Open the official source before relying on the rule for a consequential decision.

Record dates

Published
September 23, 2026
Rule verified
September 23, 2026
Review due
September 30, 2026

Challenge this record

If the source or summary appears wrong, submit precise evidence for human review.

Submit a correction