Configuration management examples for SONiC
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 57%
Response Time: -
First Timer Success: 52%
sonic-net/sonic-mgmt has a recorded first-timer success rate of 52.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in sonic-net/sonic-mgmt 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 66.3 places sonic-net/sonic-mgmt in the A tier.
The external contributor pull request merge rate for sonic-net/sonic-mgmt is 56.9%, based on public PR activity from non-core contributors.
sonic-net/sonic-mgmt currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in sonic-net/sonic-mgmt. Ensure PR scope matches issue requirements closely before requesting review.
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/sonic-net/sonic-mgmt?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 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (71% approval). Large PRs (>500 lines) take ~115 hours (26% approval). Keep your diff compact for rapid review.
Is it platform specific generic Importance or Severity High Description of the test gap For SONiC T2, we have the Linecard which is 400g SKU, but a port was configured to 100g. Now we use GCU patches to remove the 100g port and add port configuration to change the port speed to 400. This test gap is tracking to add a test for this usecase Affected Area GCU Impact of missing tests and proposed tests some of the GCU usecases remain untested
Is it platform specific broadcom Importance or Severity Low Description of the bug Some tests in drop_packets/test_drop_counters, related to invalid multicast destination MAC packets, fail on topologies using Q3D based fanout device. The below shown predefined trap on the fanout captures the packet causing the test to fail. IRPP predefined traps configured: IpCompMcInvalidIp | VTT_IP_COMP_MC_INVALID_IP(0x18) | 0 | 7 | FALSE Steps to Reproduce Run drop_packets/test_drop_counters.py test on a DUT using Q3D based fanout device. Actual Behavior and Expected Behavior Expected Behavior: This test validates that SONiC correctly drops packets with unicast IP addresses but multicast/broadcast Ethernet destination MAC addresses and properly increments the Layer 3 (L3) drop counters. Actual Behavior: The packets never reach the DUT and the test fails as the fanout traps the packets. Relevant log output FAILED drop_packets/test_drop_counters.py::test_unicast_ip_in
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 sonic-net/sonic-mgmt, 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 sonic-net/sonic-mgmt acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 56.9% were successfully merged into the primary branch.
sonic-net/sonic-mgmt has a recorded first-timer success rate of 52.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 66.3 places sonic-net/sonic-mgmt in the Welcoming tier.
The external pull request merge rate is 56.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, sonic-net/sonic-mgmt 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 sonic-net/sonic-mgmt 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.