MG SAIC Custom Integration for Home Assistant
C-Rank Grade: S (Elite) - 74/100
External PR Merge Rate: 81%
Response Time: 11h
First Timer Success: 67%
townsmcp/mg-saic-ha has a recorded first-timer success rate of 66.7%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in townsmcp/mg-saic-ha respond to incoming external pull requests in approximately 11.4 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 73.8 places townsmcp/mg-saic-ha in the S tier.
The external contributor pull request merge rate for townsmcp/mg-saic-ha is 81.0%, based on public PR activity from non-core contributors.
townsmcp/mg-saic-ha currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in townsmcp/mg-saic-ha. Reviews community pull requests with focus on project quality.
Discussions in townsmcp/mg-saic-ha 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/townsmcp/mg-saic-ha?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~7 hours (96% approval). Large PRs (>500 lines) take ~55 hours (36% approval). Keep your diff compact for rapid review.
Home Assistant Version 2026.9.4 MG/SAIC Integration Version 1.2.9 Installation Method HACS Are you on the latest release of this integration? Yes, I am running the latest version of the integration No, I have not updated the integration. Did you check for existing issues? Yes, I have checked for existing issues No, I have not checked for existing issues Did you enable debug logging before and are ready to post logs? Yes, I have enabled debug logging No, I have not enabled debug logging Describe the Issue When I try to change the temperature on the climate control it won't change and always sticks with what the app last had set so I can't heat the car if it was on cool last time or change the set temperature Logs Home Assistant Core File "/config/custom_components/mg_saic/coordinator.py", line 874, in async_setup File "/config/custom_components/mg_saic/__init__.py", line 194, in async_setup_entry File "/config/custom_components/mg_saic/__init__.py", line 355, in _async
Home Assistant Version 2026.06.2 MG/SAIC Integration Version 1.1.2 Installation Method HACS Did you check for existing issues? Yes, I have checked for existing issues No, I have not checked for existing issues Did you enable debug logging before and are ready to post logs? Yes, I have enabled debug logging No, I have not enabled debug logging Describe the Issue Although the integration provide a phone number authentication option and a "rest of the world" scope, these do not work for Thailand MG account. Logs Logger: custom_components.mg_saic Source: custom_components/mg_saic/config_flow.py:103 Integration: MG SAIC Integration (documentation, issues) First occurred: 6:38:05 PM (1 occurrence) Last logged: 6:38:05 PM Failed to authenticate or fetch vehicle data: return code: 1000036, message: The account is not registered. Logger: custom_components.mg_saic Source: custom_components/mg_saic/config_flow.py:244 Integration: MG SAIC Integration (documentation, issues) First occ
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 townsmcp/mg-saic-ha, 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 townsmcp/mg-saic-ha acknowledge new external contributions in approximately 11 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 81.0% were successfully merged into the primary branch.
townsmcp/mg-saic-ha has a recorded first-timer success rate of 66.7%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~11 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 73.8 places townsmcp/mg-saic-ha in the Elite tier.
The external pull request merge rate is 81.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, townsmcp/mg-saic-ha 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 townsmcp/mg-saic-ha 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.