Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use ros2-gbp release repository for topic_based_ros2_control. #40028

Merged
merged 1 commit into from
Mar 1, 2024

Conversation

nuclearsandwich
Copy link
Member

The repository has been mirrored into ros2-gbp here: ros2-gbp/ros2-gbp-github-org#459.

I did not change the release repository for noetic at this time since it is not required for ROS 1 distributions, but if the maintainer prefers to use a single release repository for all distributions that is perfectly acceptable.

The repository has been mirrored into ros2-gbp here: ros2-gbp/ros2-gbp-github-org#459.

I did not change the release repository for noetic at this time since it is not required for ROS 1 distributions, but if the maintainer prefers to use a single release repository for all distributions that is perfectly acceptable.
@nuclearsandwich nuclearsandwich self-assigned this Feb 29, 2024
@github-actions github-actions bot added humble Issue/PR is for the ROS 2 Humble distribution iron Issue/PR is for the ROS 2 Iron distribution rolling Issue/PR is for the ROS 2 Rolling distribution labels Feb 29, 2024
@nuclearsandwich
Copy link
Member Author

FYI @sea-bass and @sjahr (as recently active Picknik releasers).

@nuclearsandwich nuclearsandwich merged commit fcc027f into master Mar 1, 2024
4 checks passed
@nuclearsandwich nuclearsandwich deleted the rolling/ros2-gbp/topic_based_ros2_control branch March 1, 2024 00:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
humble Issue/PR is for the ROS 2 Humble distribution iron Issue/PR is for the ROS 2 Iron distribution rolling Issue/PR is for the ROS 2 Rolling distribution
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants