Why Pull Requests Get Ignored (And How to Find Repos That Merge Yours)
Every day, developers clone a popular GitHub repository, read docs, write tests, and submit a clean pull request.
And then... silence. Weeks turn into months. The PR sits untouched until merge conflicts break it. GetMerged fixes this by measuring real maintainer activity before you write a single line of code.
Most open source maintainers work unpaid in their spare time. When popular projects get overwhelmed by issues, review queues slow to a crawl.
GitHub stars accumulate over years like museum plaques. A 40,000-star project might not have reviewed a community pull request in months.
We track live GitHub pull requests, review response times, and newcomer merge rates so you can contribute with confidence.
The 9 Signals We Check
Every repository is continuously benchmarked against other projects in the same programming language ecosystem.
External PR Acceptance Rate
Are outside submissions welcomed into main?
Measures whether non-maintainer community code actually reaches production. Filters out automated dependency bots and internal branch merges.
Reviewer Response Turnaround
The 24-Hour Review Window
Calculates median hours before a maintainer leaves an actionable review. PRs that wait more than 7 days without feedback have an 80% higher abandonment rate.
Commit Rhythm & Recency
Active Maintainers vs. Stale Repos
Monitors commit activity across a rolling 180-day window, ensuring you don't spend time contributing to a project whose team stepped away.
First-Timer Contributor Success
Do new authors receive constructive onboarding?
Tracks developers opening their very first pull request. Separates supportive, mentorship-driven teams from closed, unresponsive repos.
Merge Speed & Cycle Duration
Fast turnaround without endless rebasing
Measures the time from initial opening to final merge, avoiding weeks-long cycles of unresolved merge conflicts and review stalling.
Repeat Contributor Retention
Do contributors return for PR #2 and #3?
Checks if developers enjoy their first contribution experience enough to come back. The best indicator of welcoming, supportive maintainers.
Review Cycle Efficiency
Clear guidance vs. fragmented nitpicks
Rewards teams that provide consolidated, clear review feedback in fewer rounds rather than dragging reviews out over weeks.
Active Review Team Breadth
Multiple active reviewers
Evaluates the number of active distinct reviewers. Projects with distributed review teams avoid single-maintainer bottlenecks and burnout.
Issue & Discussion Response
Proactive issue triaging and scoping
Tracks how quickly maintainers respond to questions on issues and discussions to see if they actively help new contributors get started.
How Each Metric Is Calculated
Clear, objective metrics calculated directly from public GitHub pull requests and review activity.
| Metric | Priority | Timeframe | Why It Matters |
|---|---|---|---|
| 1. External PR Merge Rate | Primary | 180-Day Rolling | Ratio of merged vs. closed outside community PRs (excludes automated bot merges). |
| 2. Initial Review Response Turnaround | High Impact | Recent PRs | Median hours before a human maintainer posts an actionable review. |
| 3. Maintainer Commit & Merge Recency | High Impact | Active Window | Ensures the core maintainers are currently active on the repository. |
| 4. First-Timer Contributor Success | Hospitality | New Authors | Acceptance rate and constructive feedback for developers opening their very first PR. |
| 5. Time to Merge (Land Velocity) | Velocity | Merged PRs | Total hours from opening a pull request to getting merged into main. |
| 6. Repeat Contributor Retention | Community | Past Year | Percentage of outside contributors who return to open a second or third PR. |
| 7. Review Cycle Efficiency | Efficiency | Per PR | Rewards consolidated, clear feedback rounds without dragged-out review churn. |
| 8. Review Team Size & Breadth | Team Health | 90-Day Active | Multi-maintainer review coverage to prevent single-person bottlenecks. |
| 9. Issue & Discussion Responsiveness | Support | Issues | Promptness and clarity when guiding prospective contributors on issues. |
The C-Rank™ Hospitality Ladder
Know what to expect before you write a single line of code.
The open doors. Pull requests receive active review within 24 hours, maintainers provide friendly guidance, and new contributor merge rates exceed 80%.
Reliable, healthy repositories with dependable review cadences. Consistent feedback and positive contributor culture.
Active maintainers who face periodic review bottlenecks around major release sprints. Review cycles typically take 3 to 7 days.
Selective code acceptance or backlogged maintainers. Best suited for seasoned developers who don't mind long turnaround delays.
Stale repositories or abandoned pull request queues. Avoid submitting PRs here unless actively requested by current maintainers.
Find your next open door today
Stop guessing which repos will merge your PRs. Browse repositories with verified maintainer pulse.