C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 88%
Response Time: 2d
First Timer Success: 100%
Giant-Bomb-Dot-Com/giant-bomb-wiki has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Giant-Bomb-Dot-Com/giant-bomb-wiki respond to incoming external pull requests in approximately 44.6 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 65.0 places Giant-Bomb-Dot-Com/giant-bomb-wiki in the A tier.
The external contributor pull request merge rate for Giant-Bomb-Dot-Com/giant-bomb-wiki is 88.2%, based on public PR activity from non-core contributors.
Giant-Bomb-Dot-Com/giant-bomb-wiki currently has 10 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in Giant-Bomb-Dot-Com/giant-bomb-wiki. Ensure PR scope matches issue requirements closely before requesting review.
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/Giant-Bomb-Dot-Com/giant-bomb-wiki?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~29 hours (96% approval). Large PRs (>500 lines) take ~214 hours (40% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in PHP.
Powerful framework for designers and developers to create responsive, fast & robust Joomla based websites and templates.
š Core of the full-text search framework for Nextcloud
CMS application written in Laravel 13 / PHP 8.5 using Filament 5 - WordPress or Drupal or OctoberCMS alternative.
If you add a Franchise to a Game page, the Franchise appears correctly on the Game page. However, the Game does not show up on the Franchise page. In the info box on the right side of the Franchise page, it DOES show the correct number of games associated with the Franchise. So, it knows somewhere that those games are tagged to it, but it does not list them. https://giantbomb.com/api/media/file/media--file--screenshot-2026-06-13-at-9-36-58-pm-06-14-2026.png Additionally, if you edit a Franchise page, no Games appear there either. And adding a Game to the Franchise page that way does nothing. https://giantbomb.com/api/media/file/media--file--screenshot-2026-06-13-at-9-36-44-pm-06-14-2026.png
There are many examples I could use, but I'll go with this one. If I search "halo", currently the top 12 results do not include any Halo games. It does however include characters named Hal, Hale, Hala, and Halko. https://giantbomb.com/api/media/file/media--file--screenshot-2026-06-13-at-9-17-50-pm-06-14-2026.png
https://giantbomb.com/api/media/file/media--file--screenshot-2026-06-13-at-8-51-24-pm-06-14-2026.png
Upon creating a page or updating the release date, it fails to appear in the info box on the right side of the game page. It does accurately appear at the top of the page under the title next to "GAME >>". It's not a normal "wait 5 or 10 minutes" caching issue. This Madden NFL 27 page was created over a week ago and it's still not there. https://giantbomb.com/wiki/Games/Madden_NFL_27
People entries are duplicated - e.g. https://giantbomb.com/wiki/People/Stephane_Assadourian_86692 https://giantbomb.com/wiki/People/Stephane_Assadourian https://giantbomb.com/wiki/People/Rajesh_G_S It's possible this is because of accent marks - unsure.
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 Giant-Bomb-Dot-Com/giant-bomb-wiki, 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 Giant-Bomb-Dot-Com/giant-bomb-wiki acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 88.2% were successfully merged into the primary branch.
Giant-Bomb-Dot-Com/giant-bomb-wiki has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. 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 65.0 places Giant-Bomb-Dot-Com/giant-bomb-wiki in the Welcoming tier.
The external pull request merge rate is 88.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Giant-Bomb-Dot-Com/giant-bomb-wiki currently has 10 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for Giant-Bomb-Dot-Com/giant-bomb-wiki 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.