This repository aims at providing examples to illustrate ros2_control and ros2_controllers
C-Rank Grade: A (Welcoming) - 68/100
External PR Merge Rate: 58%
Response Time: -
First Timer Success: 17%
ros-controls/ros2_control_demos has a recorded first-timer success rate of 16.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ros-controls/ros2_control_demos 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 67.8 places ros-controls/ros2_control_demos in the A tier.
The external contributor pull request merge rate for ros-controls/ros2_control_demos is 58.1%, based on public PR activity from non-core contributors.
ros-controls/ros2_control_demos currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (66% critical review signals). Ensure PRs strictly follow guidelines before requesting review in ros-controls/ros2_control_demos.
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/ros-controls/ros2_control_demos?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (73% approval). Large PRs (>500 lines) take ~115 hours (26% approval). Keep your diff compact for rapid review.
Background Refactor the urdf tests like https://github.com/ros-controls/ros2_control_demos/blob/master/example_1/test/test_urdf_xacro.py to use https://github.com/pal-robotics/urdf_test Instructions Hi, this is a good-first-issue issue. This means we've worked to make it more legible to people who either haven't contributed to our codebase before, or even folks who haven't contributed to open source before. We're interested in helping you take the first step, and can answer questions and help you out along the way. Note that we're especially interested in contributions from underrepresented groups! We know that creating a pull request is the biggest barrier for new contributors. This issue is for you 💝 If you have contributed before, consider leaving this PR for someone new, and looking through our general bug issues. Thanks! 🤔 What you will need to know. Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process. 📋 Step by Step
We currently test only if the systems (hardware+controllers) are launched correctly. But there is no test if the robots actually move. This leads to issues with configuration, like reported in #1086 We can use a similar pattern like in gz_ros2_control_tests and adapt them to the demos.
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 ros-controls/ros2_control_demos, 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 ros-controls/ros2_control_demos acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 58.1% were successfully merged into the primary branch.
ros-controls/ros2_control_demos has a recorded first-timer success rate of 16.7%. 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 67.8 places ros-controls/ros2_control_demos in the Welcoming tier.
The external pull request merge rate is 58.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ros-controls/ros2_control_demos currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for ros-controls/ros2_control_demos 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.