The open-source repo for docs.github.com
C-Rank Grade: B (Solid) - 51/100
External PR Merge Rate: 23%
Response Time: 18h
First Timer Success: 21%
github/docs has a recorded first-timer success rate of 20.7%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in github/docs respond to incoming external pull requests in approximately 17.7 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 51.1 places github/docs in the B tier.
The external contributor pull request merge rate for github/docs is 23.3%, based on public PR activity from non-core contributors.
github/docs does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Rigorous architecture standards (80% critical review signals). Ensure PRs strictly follow guidelines before requesting review in github/docs.
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/github/docs?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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~11 hours (29% approval). Large PRs (>500 lines) take ~85 hours (15% approval). Keep your diff compact for rapid review.
Code of Conduct I have read and agree to the GitHub Docs project's Code of Conduct What article on docs.github.com is affected? https://docs.github.com/en/code-security/reference/supply-chain-security/dependabot-options-reference#labels-- https://docs.github.com/en/code-security/tutorials/secure-your-dependencies/customizing-dependabot-prs (its default-labels text comes from data/reusables/dependabot/default-labels.md) What part(s) of the article would you like to see updated? The two articles describe Dependabot's default labels in ways that contradict each other: When the ecosystem label is added. The options reference (labels → "Dependabot default behavior") says the ecosystem label is added only when more than one package manager is defined. The customizing article (the default-labels reusable) says both the dependencies label and the ecosystem label are added to all pull requests, single-ecosystem updates included. Both can't be right; the observed behavior matches the se
Code of Conduct I have read and agree to the GitHub Docs project's Code of Conduct What article on docs.github.com is affected? Dependabot TSG: Pull request limit reached error vs. dependabot.yml options reference: open-pull-requests-limit key What part(s) of the article would you like to see updated? The dependabot.yml reference has this note: "Security update pull requests are not subject to this limit and do not count toward it. There is no limit on the number of open pull requests for security updates." The context of this note is within the open-pull-requests-limit section and as I've understood it, the first sentence is true. However, the second sentence seems to conflict with the TSG which calls out a hard limit of 10 open security update PRs. My confusion - does this maximum for open security update PRs exist? If yes, then the second sentence in the note should either be removed or tweaked to something like "The hard limit of 10 open PRs for security updates is not configur
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 github/docs, 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 github/docs acknowledge new external contributions in approximately 17 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 23.3% were successfully merged into the primary branch.
github/docs has a recorded first-timer success rate of 20.7%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~17 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 51.1 places github/docs in the Solid tier.
The external pull request merge rate is 23.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
github/docs does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for github/docs 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.