Philippines staffing research ·

What pull request review latency leaves out

What pull request review latency leaves out

Separate waiting, active review, author response, and release holds.

A pull request can remain open while a reviewer is unavailable, the author is revising it, a check is blocked, or a release is on hold. One elapsed-time number combines those states.

GitHub documents review states and approvals. DORA studies delivery as a system. Neither source defines a universal acceptable review time.

Methodology: select one repository and fixed period. Record creation, review request, first substantive review, requested changes, author response, approval, closure, merge, draft periods, and check waits. Publish sample size and exclusions.

Scope and inference boundaries: results describe the sampled repository, team, and period. They may identify where work waited. They do not measure review quality, productivity, task difficulty, or business value.

Limitations: timestamps omit some conversations. Bots, reopened work, time zones, and small samples distort comparisons. Keep those cases visible. The company owner decides staffing, review policy, and release timing.

Sources

  1. GitHub Docs: pull request reviews
  2. DORA research

Related Research

FAQ

What should happen first?

Begin with a bounded ticket, approved access, and a named reviewer.

Who approves production changes?

The company’s technical owner keeps final merge and release authority.