Blog

Data-driven writing on code review performance: merge latency, bottlenecks, backlog pressure, tail risk, and engineering metrics.

• GitHub Capped Open Pull Requests. The Stale Queue Is Still Invisible. — On 6 August 2026 GitHub let organizations cap how many open PRs a user without write access can have at once. That throttles intake. It does not show which open PRs have already gone idle.
• Review Depth Is Now an Organization Setting: What to Measure Before You Pick a Default — On 7 August 2026 GitHub made Copilot code review effort levels generally available, including an organization-wide default that every repository inherits. How much review should your organization do? What to measure before you pick a default.
• GitHub Stacked Pull Requests: What Shipped and What to Measure — On 30 July 2026 GitHub put stacked pull requests into public preview: a chain of small PRs that depend on each other, instead of one huge change. Small PRs are easier to review. You still need to watch the large ones, not just typical size.
• Your Cycle Time Is One Number. Your PR Pipeline Has Four Stages. — A July 2026 CMU/Stanford study of 196,212 pull requests had to split the wait into stages before it could say where delivery time actually goes. GitQuick's Pipeline view does the same per org — and across eighteen public showcase orgs, the stage that looks fastest is often just the one with the most bots in it.
• Pull Request Review Latency: How to Measure It and Find Bottlenecks — Define pull request review latency by stage — time to first review, approval, and approval-to-merge — and use median vs P90 to find where the process actually stalls.
• More PRs Open Than Close? Your Review Queue Is Growing — Cycle time can look excellent while the queue keeps growing. Google Cloud's showcase window pairs a 17-minute typical first review and a 2.6-hour typical merging time with merge efficiency of 1.77 — and across seventeen public orgs, review latency and backlog growth barely correlate at all.
• Your PRs Are Approved. Why Aren't They Merging? — Everyone watches review latency. Almost nobody watches the gap between the green checkmark and the merge. Across public organizations showcases, median approval-to-merge is minutes, but the P90 tail runs hours to over a day, and GitQuick's Merge Pipeline Friction signal fires on every one of them.
• Stop Reading Dashboards: Eight Signals That Tell You What's Wrong With Code Review — GitQuick's Signals tab turns review metrics into a weekly playbook — deterministic checks, evidence-aware actions, PR drill-downs, and cross-run badges that show what's new, worsening, or stuck.
• Half Your Merges Might Have Zero Review. Do You Know the Number? — Zero-review merges are up 31% industry-wide even as Copilot runs 60M reviews. GitQuick showcase data from ten major open-source orgs shows the range - from 0.1% to 52.4% - and why most teams still do not track it.
• The Bottleneck Moved. Your Metrics Probably Didn't. — AI coding tools boosted commits by 180%, but releases only rose 30%. Recent engineering debates and real PR data from major open-source organizations point to the same problem: code review is becoming the new delivery constraint.
• More AI Doesn't Guarantee Better Software But It Seems to Guarantee Faster Iteration — A data-driven analysis of AI-assisted code review, review automation, merge times, and pull request velocity across ten major open-source organizations.
• We Analyzed 10,000+ OSS Pull Requests from AWS and GoogleCloudPlatform. Here's What Their Review Pipelines Reveal. — GCP moves faster. AWS looks more governed. The useful question is not who "wins", but what engineering teams can learn from both review pipelines, and what actions we recommend to mend the gap.
• GitHub Doesn't Tell You How Your Code Reviews Are Actually Going — The platform hosts millions of PRs but gives teams zero insight into review performance. Here's what you're missing.
• Your Code Reviews Are Slower Than You Think — Why teams underestimate review speed: selective memory, weekend blind spots, and averages that hide the long tail — and what to measure instead.
• The Pseudo-Bot Reviewer — In mid-April, he was #2 on the reviewer leaderboard. Six weeks later, he was #1 - with two bots right behind him, operating at roughly the same scale.