The Wikimedia Commons Android app allows users to upload pictures from their Android phone/tablet to Wikimedia Commons
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 35%
Response Time: -
First Timer Success: 22%
commons-app/apps-android-commons has a recorded first-timer success rate of 22.2%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in commons-app/apps-android-commons 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 59.7 places commons-app/apps-android-commons in the A tier.
The external contributor pull request merge rate for commons-app/apps-android-commons is 34.6%, based on public PR activity from non-core contributors.
commons-app/apps-android-commons currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in commons-app/apps-android-commons. Maintains strict focus on technical quality and test standards.
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/commons-app/apps-android-commons?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 10:00 to 14:00 UTC (10:00 - 14:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (43% approval). Large PRs (>500 lines) take ~115 hours (16% approval). Keep your diff compact for rapid review.
What is the user problem or growth opportunity you want to see solved? No response How do you know that this problem exists today? Why is this important? No response Who will benefit from it? No response Anything else you would like to add? No response
https://github.com/commons-app/apps-android-commons/blob/main/.github/workflows/auto_assign.yml could be improved based on this part of our documentation: If you are a new contributor, please only ask to be assigned to issues with a "Bug" type or "good first issue" label. Issues of type "Feature" will usually only be assigned to contributors with more than 5 merged pull requests to this repo. The message could be: Thank you for your enthusiasm! While we appreciate your interest in fixing this issue, we found out that contributors who are not veterans learn better from fixing bugs (issues with Type=Bug) or working on good first issues (issues with Label=good first issue). Our documentation contains the details and a link to an issue search that gives you the best issues to work on. Would you mind trying that? Once you have found a suitable issue you want to solve, you can ask to be assigned there. Thanks a lot!
856510a8-2c99-4a81-bb84-fb072f28db81.mp4 f5eb5f50-627b-43c6-b57e-461b12b89492.mp4
I am surprised our CI did not catch this basic mistake: #6822
Description It appears that the CI workflow responsible for welcoming new contributors is consistently being skipped. As a result, first-time contributors are not receiving the intended welcome message. Expected Behavior The workflow should trigger for first-time contributors and post a welcome message automatically. Actual Behavior The workflow is skipped, even when a new contributor opens their first PR. See this PR CI : #6747 Steps to Reproduce Create a pull request from a first-time contributor account Observe the CI workflow execution Notice that the welcome workflow is skipped
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 commons-app/apps-android-commons, 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 commons-app/apps-android-commons acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 34.6% were successfully merged into the primary branch.
commons-app/apps-android-commons has a recorded first-timer success rate of 22.2%. 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 59.7 places commons-app/apps-android-commons in the Welcoming tier.
The external pull request merge rate is 34.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, commons-app/apps-android-commons currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for commons-app/apps-android-commons 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.