A Weather app for android with multiple sources 🌦🌞☔
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 74%
Response Time: -
First Timer Success: 33%
PranshulGG/WeatherMaster has a recorded first-timer success rate of 33.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in PranshulGG/WeatherMaster 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 58.8 places PranshulGG/WeatherMaster in the A tier.
The external contributor pull request merge rate for PranshulGG/WeatherMaster is 74.4%, based on public PR activity from non-core contributors.
PranshulGG/WeatherMaster does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Responsive & active maintainer team in PranshulGG/WeatherMaster. Reviews pull requests with focus on project architectural goals.
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/PranshulGG/WeatherMaster?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (93% approval). Large PRs (>500 lines) take ~115 hours (33% approval). Keep your diff compact for rapid review.
Problem Statement First off, thank you for making such a good weather app, I just wanted to make a suggestion. My phone (s23) likes to keep the app open permanently in memory but the issue is if I check the weather a day later it still shows as if yesterday's weather is current and I don't often notice. (I'm not talking about background updates, but when the app returns to the foreground while residing in memory) Proposed Solution I saw you have code that updates the weather after 45 mins after re-opening but I wonder if Android also has an on resume event when the app returns to the foreground? If you moved the code to on resume, it would trigger both when the app opens and also when it is resumed from memory. Alternatives Considered No response Additional Context I saw this was raised in #930 and marked as completed. however, I don't think the cause was explained clearly as the issue is how the app behaves after resuming from memory, not cold start events. This issue can be replicat
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 PranshulGG/WeatherMaster, 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 PranshulGG/WeatherMaster acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 74.4% were successfully merged into the primary branch.
PranshulGG/WeatherMaster has a recorded first-timer success rate of 33.3%. 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 58.8 places PranshulGG/WeatherMaster in the Welcoming tier.
The external pull request merge rate is 74.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
PranshulGG/WeatherMaster 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 PranshulGG/WeatherMaster 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.