-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Pull all example launchfiles into separate file with literalinclude
#5155
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
Pull all example launchfiles into separate file with literalinclude
#5155
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.
lgtm with :language:
extension adding. we already have literalinclude
everywhere, i think this is good for maintenance.
Signed-off-by: Emerson Knapp <[email protected]>
Signed-off-by: Emerson Knapp <[email protected]>
Signed-off-by: Emerson Knapp <[email protected]>
Signed-off-by: Emerson Knapp <[email protected]>
Signed-off-by: Emerson Knapp <[email protected]>
Signed-off-by: Emerson Knapp <[email protected]>
Signed-off-by: Emerson Knapp <[email protected]>
Signed-off-by: Emerson Knapp <[email protected]>
Signed-off-by: Emerson Knapp <[email protected]>
Signed-off-by: Emerson Knapp <[email protected]>
df921bd
to
11d6be1
Compare
Do you intend to backport this? It would be very painful, but it would avoid future merge conflicts when backporting. |
Signed-off-by: Emerson Knapp <[email protected]>
Ermmm, yeah I could do the backport to Humble and Jazzy. It's already been very painful lol |
Signed-off-by: Emerson Knapp <[email protected]>
We can merge it to rolling first though, and I can take the backports from there? I have some followup diffs I'd like to get started on. |
Feel free to merge it if it's ready. I've added the backport-all label, let's just see how it goes. |
It is ready - I do not have merge access on this repository, I need you to press it for me :) |
…#5155) Signed-off-by: Emerson Knapp <[email protected]> (cherry picked from commit 666df3e) # Conflicts: # source/Tutorials/Intermediate/Launch/Using-Event-Handlers.rst # source/Tutorials/Intermediate/Launch/Using-Substitutions.rst
…#5155) Signed-off-by: Emerson Knapp <[email protected]> (cherry picked from commit 666df3e) # Conflicts: # source/How-To-Guides/Launch-file-different-formats.rst # source/Tutorials/Intermediate/Launch/Using-Event-Handlers.rst # source/Tutorials/Intermediate/Launch/Using-ROS2-Launch-For-Large-Projects.rst # source/Tutorials/Intermediate/Launch/Using-Substitutions.rst # source/Tutorials/Intermediate/Tf2/Adding-A-Frame-Cpp.rst # source/Tutorials/Intermediate/Tf2/Adding-A-Frame-Py.rst
…nclude (backport #5155) (#5179) Signed-off-by: Emerson Knapp <[email protected]> (cherry picked from commit 666df3e) * Resolve merge conflicts
…include (backport #5155) (#5183) Signed-off-by: Emerson Knapp <[email protected]> (cherry picked from commit 666df3e) * Fix up the rest of the tutorial launchfile merges
Part of #5143
This way we can easily grab them for testing, manipulate programmatically, share without repeating (especially in block-by-block code walkthroughs), and maybe even run linters on them at some point to apply ROS 2 coding standards and maintain a consistent formatting.
I resisted the temptation to rewrite them, except for minor formatting fixes.