Skip to content

Learning about parameters - tutorial - #7031

Merged
fujitatomoya merged 13 commits into
ros2:rollingfrom
kacperbojakowski-3di:learning-about-parameters-tutorial
Aug 1, 2026
Merged

Learning about parameters - tutorial#7031
fujitatomoya merged 13 commits into
ros2:rollingfrom
kacperbojakowski-3di:learning-about-parameters-tutorial

Conversation

@kacperbojakowski-3di

Copy link
Copy Markdown
Contributor

Updated the article "Learning about parameters - tutorial".

This update is part of #6827.

Description

Related to: ros2/ros2#1725

  • Title changed to "Learning about parameters - tutorial".
  • Sections rewritten to reflect the new content model.
  • Replaced command-named headings with task-oriented headings.
  • Reworded explanations for clarity.
  • Clarified expected terminal output by separating sample results into their own console blocks.
  • Clarified that omitting the node name with ros2 param get works only on Lyrical, Rolling, and later.
  • Added an FAQ section and related content.
  • Tested on Ubuntu. The underlying procedures are unchanged.

Did you use Generative AI?

Yes, GPT-5 for the FAQ section.

Additional Information

Documentation updates from 3di Information Solutions, agreed with Geoff and Tully.

Label

Please add backport-lyrical.

@kscottz kscottz left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

This is fine as is. My only concern is that if we are touching this tutorial we really should add a section that asks the user to run ros2 param --help. Most of the intro tutorials really should be showing users how they can help themselves figure out a command.

@mergify

mergify Bot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

  • Queue this pull request

@fujitatomoya fujitatomoya left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

lgtm with green CI.

@fujitatomoya
fujitatomoya merged commit a3e6767 into ros2:rolling Aug 1, 2026
7 checks passed
@fujitatomoya fujitatomoya added the backport-all backport at reviewers discretion; from rolling to all versions label Aug 1, 2026
@fujitatomoya

Copy link
Copy Markdown
Collaborator

@kacperbojakowski-3di thanks for the PR, all the backports to the downstream branches have some conflicts. can you resolve those?

@kacperbojakowski-3di

Copy link
Copy Markdown
Contributor Author

Backport conflicts resolved via fresh PRs (no write access to push onto the Mergify branches):

Each keeps only the parameters tutorial rewrite on the Tutorials/Beginner-CLI-Tools path with legacy doc links. The Rolling-only How-ROS-Works / ROS-Framework.rst additions from the cherry-pick were dropped.

@kacperbojakowski-3di

Copy link
Copy Markdown
Contributor Author

@kacperbojakowski-3di thanks for the PR, all the backports to the downstream branches have some conflicts. can you resolve those?

Hi @fujitatomoya,

Thanks! Sorry for the noise with extra requests, but apparently I don’t have the write access to push onto Mergify branches, so instead I opened four clean replacement backports:

You can merge those, and then the conflicted Mergify PRs can be closed. Unless I should have handled this differently, then let me know.

The big caveat here is that I have resolved these with the assumption that the structure on lyrical, kilted, jazzy and humble stays as is, but eventually the topic is going to change its position once #6998 is backported.

@dmarshant FYI, not sure how you would like to go about this.

@fujitatomoya

fujitatomoya commented Aug 6, 2026

Copy link
Copy Markdown
Collaborator

@kacperbojakowski-3di thanks for creating backports.

before moving on to review indivisual backport PRs, something i want to confirm here.

i think we need to backport #6998 in lyrical (and downstream branches) in the 1st place? that said, we can avoid those conflicts during brackports. to keep the consistency and maitainability (this is exactly why the conflicts are happening), i say we need to backport #6998 to the downstream branches in the 1st. what is your plan with OSRA ROS TGC?

CC: @kscottz @gbiggs @mjcarroll @ahcorde

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-all backport at reviewers discretion; from rolling to all versions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants