-
Notifications
You must be signed in to change notification settings - Fork 195
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
fix link to recently-moved MoveIt for ROS 1 tutorials #901
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good starting point. But there are many more references to the old ros-planning org.
I think a PR should address all of them.
My immediate concern was to get the MoveIt ROS one reference back working for users, not to fix the migration for the whole repository, with CI broken for different unrelated reasons at the moment. But fair enough. I went through the repo with a few One thing that popped up is that the github container registry is not migrated (yet?), e.g., |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
CI is currently failing because of ros2_kortex, which needs Kinovarobotics/ros2_kortex#159. I'll push a branch to generate new docker images, the registry is working as intended. |
As noted here: https://discourse.ros.org/t/move-of-nav2-and-moveit-repositories-at-github/37450/21?u=v4hn