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

Removed ros1 tutorials from ros2 branch #153

Merged
merged 1 commit into from
Jun 5, 2023

Conversation

ahcorde
Copy link

@ahcorde ahcorde commented May 24, 2023

According with this comment #109 (comment) these tutorials are located in a different place. We should remove them from here to avoid inconsistencies

Signed-off-by: Alejandro Hernández Cordero <[email protected]>
@ahcorde ahcorde requested a review from clalancette May 24, 2023 16:08
@ahcorde ahcorde self-assigned this May 24, 2023
@ahcorde
Copy link
Author

ahcorde commented Jun 1, 2023

friendly ping @clalancette

Copy link

@clalancette clalancette left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me with green CI.

@ahcorde I hope you don't mind if I ask for one more favor in connection with this repository. In particular, in the distribution.yaml entry that corresponds to this repository, the top-level key is called turtlesim. That means that when we go to bloom-release this package, we always have to do bloom-release turtlesim. But that is in contrast to basically all other packages, where you always need to use the name of the repository, not the package. That is, it makes more sense to me to be able to do bloom-release ros_tutorials, and have turtlesim be one of the packages. If you could look into fixing that, it would be much appreciated.

@ahcorde ahcorde merged commit e960608 into rolling Jun 5, 2023
@ahcorde ahcorde deleted the ahcorde/remove/ros1_tutorials branch June 5, 2023 13:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants