Wiki Education Foundation's Wikipedia course dashboard system
C-Rank Grade: S (Elite) - 75/100
External PR Merge Rate: 78%
Response Time: 5h
First Timer Success: 100%
WikiEducationFoundation/WikiEduDashboard has a recorded first-timer success rate of 100.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in WikiEducationFoundation/WikiEduDashboard respond to incoming external pull requests in approximately 5.2 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 75.5 places WikiEducationFoundation/WikiEduDashboard in the S tier.
The external contributor pull request merge rate for WikiEducationFoundation/WikiEduDashboard is 78.0%, based on public PR activity from non-core contributors.
WikiEducationFoundation/WikiEduDashboard currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in WikiEducationFoundation/WikiEduDashboard welcoming community pull requests and bug fixes.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/WikiEducationFoundation/WikiEduDashboard?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 19:00 UTC (19:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 19:00 to 23:00 UTC (19:00 - 23:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~25 hours (35% approval). Keep your diff compact for rapid review.
Currently, the Wikidata stats card shown for courses that have Wikidata edits is pretty overpowering, in terms of the layout and design. A few independent changes would help to start out with: It should be collapsible, and collapsed by default for courses where the home wiki is not Wikidata. All entries with 0 edits should not be rendered, and the entire category should not be rendered if all the entries within are 0. (Relatedly, a more complete design refresh is still wanted: #6877 )
Current Behavior: Currently, admins have access to a "Manage course flags" view that easily allow them to set needs_update to 1 for a given course. That's a good way to force a new full update for historical courses that ended more than 30 days ago and won't be queued automatically again otherwise. The problem with this is that, after a full update, pageviews are always zero. This is undesirable but it's expected due to a circular dependency between updating average pageviews, and updating caches. See PR #6456 Desired Behavior: Admins should be provided with a way for enqueuing a non-full update for a historical course, so that the pageviews gets populated. I usually do that by manually updating the course_wiki_timeslices table and set an empty timeslice with needs_update to 1. That makes the course to be queued again for a "normal" update so pageviews metrics are calculated. But ideally we should have a cleaner way of doing that, maybe having an admin view to manually enqueue an upda
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to WikiEducationFoundation/WikiEduDashboard, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of WikiEducationFoundation/WikiEduDashboard acknowledge new external contributions in approximately 5 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 78.0% were successfully merged into the primary branch.
WikiEducationFoundation/WikiEduDashboard has a recorded first-timer success rate of 100.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 75.5 places WikiEducationFoundation/WikiEduDashboard in the Elite tier.
The external pull request merge rate is 78.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, WikiEducationFoundation/WikiEduDashboard currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for WikiEducationFoundation/WikiEduDashboard are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.