This tool does the complicated bits for the itzg/minecraft-server image
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 86%
Response Time: 2h
First Timer Success: 100%
itzg/mc-image-helper 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 itzg/mc-image-helper respond to incoming external pull requests in approximately 1.9 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 64.2 places itzg/mc-image-helper in the A tier.
The external contributor pull request merge rate for itzg/mc-image-helper is 85.7%, based on public PR activity from non-core contributors.
itzg/mc-image-helper currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in itzg/mc-image-helper. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in itzg/mc-image-helper focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/itzg/mc-image-helper?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 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 17:00 to 21:00 UTC (17:00 - 21:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~9 hours (39% approval). Keep your diff compact for rapid review.
I have disconnected the Gradle checkReadme task from check since the output of updateReadme is showing deltas like the following, with or without the use of order parameter in @Option Index: README.md IDEA additional info: Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP <+>UTF-8 =================================================================== diff --git a/README.md b/README.md --- a/README.md (revision 4c4c5c47ce7dfa722a75d34c9eaf33f7366ff3de) +++ b/README.md (date 1791059458545) @@ -167,7 +167,7 @@ [--mod-loader=<modLoaderType>] [-o=DIR] [[--api-cache-ttl=OPERATION=DURATION]... [--api-cache-default-ttl=DURATION]] - [[--wiretap] [--use-http2]] [REF[, + [[--use-http2] [--wiretap]] [REF[, |<nl>REF...]...] Download and manage individual
It will require/assume a Forge installation ran before it First implementation can just pull the latest release from github It will drop manifest to track what version was installed before and detect the need to upgrade On upgrade, remove the libraries directory and run new installer Like Forge, etc subcommand, produce a results file that will contain modified SERVER env var
Should plan on using https://github.com/minio/minio-java to maximize portability with other s3 compatible object stores. Will need to accept client ID and secret as environment variables so I don't want a bunch of call sites in itzg/minecraft-server to need to be modified. Using env vars is quite typical in this codebase via picocli.
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 itzg/mc-image-helper, 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 itzg/mc-image-helper acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 85.7% were successfully merged into the primary branch.
itzg/mc-image-helper 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 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 64.2 places itzg/mc-image-helper in the Welcoming tier.
The external pull request merge rate is 85.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, itzg/mc-image-helper currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for itzg/mc-image-helper 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.