PR Leaderboard — June 10–13, 2026
Weekly PR repair leaderboard consolidation. Tracking impact across 6 repos over 4 days.
Pipeline Status (4-Day Aggregate)
- PRs/day: 2 ➡️ (stable)
- Total PRs: 8 (merged: 1, all-time streak: 0)
- All-time merge rate: 14% (stable)
- Repos touched: 6 over the week
- Active days: June 10, 11, 12, 13
Daily Trend
| Date | Total PRs | Merged | Merge Rate | Repos | Leader |
|---|---|---|---|---|---|
| Jun 10 | 7 | 1 | 17% | 5 | TypeScript (5.0) |
| Jun 11 | 7 | 1 | 17% | 5 | TypeScript (5.0) |
| Jun 12 | 8 | 1 | 17% | 6 | TypeScript (5.0) |
| Jun 13 | 8 | 1 | 14% | 6 | TypeScript (5.0) |
Merge rate dropped from 17% → 14% on June 13 as new PRs accumulated without additional merges.
🏆 Weekly Leaderboard
🥇 microsoft/TypeScript — Impact Score: 5.0
- PRs: 2 submitted, 1 merged (50%)
- Category: typescript-js
- Difficulty: 🟢2
- Merged: ✅ #63480 — PR (bug-fix)
- Pending: ⏳ #25083 — PR (bug-fix, 🧪❓)
- Trend: ➡️ (stable leader all week)
🥈 cookiecutter/cookiecutter — Impact Score: 2.0
- PRs: 2 submitted, 0 merged (0%)
- Category: sci-data
- Difficulty: 🟢2
- Tests: 🧪 All tests verified
- Pending: ⏳ #2219 — PR, ⏳ #2217 — PR
🥉 BurntSushi/ripgrep — Impact Score: 1.0
- PRs: 1 submitted, 0 merged (0%)
- Category: wildcard
- Difficulty: 🟢1
- Tests: 🧪 All tests verified
- Pending: ⏳ #3222 — PR
#4 psf/requests — Impact Score: 1.0
- PRs: 1 submitted, 0 merged (0%)
- Category: web-api
- Difficulty: 🟢1
- Tests: 🧪 All tests verified
- Pending: ⏳ #6102 — PR
#5 gitleaks/gitleaks — Impact Score: 1.0
- PRs: 1 submitted, 0 merged (0%)
- Category: security
- Difficulty: 🟡1
- Tests: 🧪⚠️ Missing test records
- Pending: ⏳ #2121 (medium, 🧪❓)
#6 sympy/sympy — Impact Score: 1.0 (added Jun 12)
- PRs: 1 submitted, 0 merged (0%)
- Category: sci-data
- Difficulty: 🟢1
- Tests: 🧪⚠️ Missing test records
- Pending: ⏳ #24026 — PR
⚠️ Failure Analysis
Persistent issues (all 4 days):
- microsoft/TypeScript — One PR merges (#63480), one stays pending (#25083 with missing test records)
- wildcard category — ripgrep diff generated but PR never opened on GitHub (push-pr step issue)
- No reviews on any open PRs across all 4 days
- Missing test records on TypeScript, gitleaks, and sympy PRs
Regression on Jun 13: Merge rate dropped 17% → 14%. Root cause: new PRs accumulated (sympy added) without any additional merges, diluting the ratio.
Methodology
This weekly consolidation aggregates daily snapshots from the PR tracking dataset in benchmark-tracker.json [[1]]. Each PR entry records the repo, issue number, fix type, difficulty classification, test results, and merge status. Impact score is a weighted composite: merged PRs weighted 3x, submitted PRs weighted 1x. Trend direction compares each day’s score against the previous day’s snapshot from leaderboard-archive.json [[1]].
The dataset covers 6 active repos. PRs are tracked from submission through review, merge, or abandonment. Difficulty is assigned by the patch generator based on fix line count and code change complexity. Test status reflects automated CI results from the runner environment [[1]].
References
[1] PR tracking dataset — benchmark-tracker.json. https://github.com/techgeek/code-intel-blog/blob/main/production-patches/benchmark-tracker.json