-
Notifications
You must be signed in to change notification settings - Fork 36
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
Point users to space_robots
demo at the end of moveit2
README (#85)
#84
Point users to space_robots
demo at the end of moveit2
README (#85)
#84
Conversation
@sea-bass We are now following a process described in https://github.com/space-ros/space-ros/blob/main/CONTRIBUTING.md. Could I trouble you to please open an issue detailing what's missing/wrong about the current instructions, so that we can associate this PR to it (including mentioning the issue by number in the summary line of the commit itself) before we merge it? Thanks! |
@ivanperez-keera Done -- linked to an issue. Do you mind answering my open question in the PR description in case we want to also tackle that in this PR vs. take no action? Thanks! |
I agree with removing the |
Could you also adjust the commit message to point to the issue the way we are doing this in other commits? (Sorry, I saw your comment but we are relying on commits to point to issues, not github's method of linking things.) |
This issue addresses multiple concerns (typos, like breaking, the |
@ivanperez-keera since @sea-bass isn't really working on Space ROS and was just doing us a favor as part of the first release you might need to be the change you want to see in the PR on this one. Also can you clarify if you want the different types of changes you mentioned broken up to different issues, PRs, commits, or some combination? |
I'm happy to split these up this week, but would agree that having the list of which parts to break down would be useful. I'm seeing:
Does this sound good? |
Hi @sea-bass. Sorry that it took me a bit longer. Thanks a lot for your understanding of our process and for showing flexibility 😃 . We're trying our best to be thorough. I've split this into several issues:
EDIT: Changed because I went ahead and filed PRs for the smaller things. @sea-bass Can you please modify this this PR (number #84), to retain only the changes pertaining to #85 specifically (the relation between the Moveit2 and the Robots demos), without any style, formatting or typo changes. |
space_robots
demo at the end of moveit2
README
92f4eb3
to
4230bb8
Compare
4230bb8
to
30f3636
Compare
@ivanperez-keera thank you for doing a lot of this PR surgery on my behalf -- much appreciated. I've updated this PR to only address #85. |
Thank you, @sea-bass . Merging. |
space_robots
demo at the end of moveit2
READMEspace_robots
demo at the end of moveit2
README (#85)
I was doing some testing with these Docker images to give an official MoveIt maintainer sign-off for working MoveIt2 images.
I was able to run both the MoveIt2 Tutorials RViz example as per the
moveit2
image, and also the Canadarm demo in thespace_robots
image.Just submitting a few small tweaks based on my trying to follow the instructions, but otherwise 👍🏻
Closes #85
Quick question -- can I also remove all the
$
from all the README Instructions, likebecause it makes it annoying to copy paste -- I have to manually select the text or remove the first few characters instead of copying the entire line.