TripleA is a turn based strategy game and board game engine, similar to Axis & Allies or Risk.
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 86%
Response Time: -
First Timer Success: 60%
triplea-game/triplea has a recorded first-timer success rate of 60.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in triplea-game/triplea respond to incoming external pull requests in approximately 0.0 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 67.4 places triplea-game/triplea in the A tier.
The external contributor pull request merge rate for triplea-game/triplea is 86.4%, based on public PR activity from non-core contributors.
triplea-game/triplea currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in triplea-game/triplea. Reviews community pull requests with focus on project quality.
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/triplea-game/triplea?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 23:00 UTC (23:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 22:00 to 02:00 UTC (22:00 - 02:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (39% approval). Keep your diff compact for rapid review.
I was playing with a friend in the new version of tripleA (version 2026-08.16.15740) on map-WWII v3 1941. We used low luck for combats but not for AA guns. So it happens that there is no way to avoid low luck on AA guns if you play this way. We had to do it manually and edit the s**t out of all the battles/bombing that involved more than one airplane.
When the Purchase phase/delegate is presented on screen, show the new 'factory' scroller. This would benefit all maps but especially random start maps, it would be great to cycle through all the factory units like isFactory and units that have canProduceUnits or canProduceXUnits in Territories/Sea Zones Sometimes the xml code can have isFactory or canProduceUnits or canProduceXUnits, but only count the unit once. . This map, is the most complicated and has random start with the following; non moving units that can produce units Castle, Urban, BreedingGround, Portal, Sorcerer-Tower moving units Sorcerer, Ancient-Dragon, Dragon, Young-Dragon, Demonship Download it here https://forums.triplea-game.org/topic/2467/settlers-fallen-empire-official-thread I can/will help test the map. Other maps that would greatly benefit are; 1888a Steam & Steel - random start Shogun Advanced - random start Greyhawk Wars - moving heroes that are 'Factory' WW2 maps, player is Britain as they have 'Factory'
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 triplea-game/triplea, 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 triplea-game/triplea acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 86.4% were successfully merged into the primary branch.
triplea-game/triplea has a recorded first-timer success rate of 60.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 67.4 places triplea-game/triplea in the Welcoming tier.
The external pull request merge rate is 86.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, triplea-game/triplea currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for triplea-game/triplea 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.