Skip to content

Improve ros2 lifecycle set transition help - #1271

Open
sylvesterkaczmarek wants to merge 1 commit into
ros2:rollingfrom
sylvesterkaczmarek:fix-122-lifecycle-set-help
Open

Improve ros2 lifecycle set transition help#1271
sylvesterkaczmarek wants to merge 1 commit into
ros2:rollingfrom
sylvesterkaczmarek:fix-122-lifecycle-set-help

Conversation

@sylvesterkaczmarek

@sylvesterkaczmarek sylvesterkaczmarek commented Aug 20, 2026

Copy link
Copy Markdown

Summary

Fixes #122.

Improve the ros2 lifecycle set transition argument help so users are pointed directly to ros2 lifecycle list NODE_NAME, which reports transitions available from the node's current state.

This avoids duplicating a static transition list in help text and uses the existing lifecycle query command.

Validation

  • Help-text-only change
  • Branch is one signed commit and one file ahead of Rolling

Did you use Generative AI?

Yes. AI was used to assist with tests.

Signed-off-by: Sylvester Kaczmarek <16242628+sylvesterkaczmarek@users.noreply.github.com>
@mergify

mergify Bot commented Aug 20, 2026

Copy link
Copy Markdown

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

  • Queue this pull request

@fujitatomoya

Copy link
Copy Markdown
Collaborator

i assume you are using AI agent to create this PR, that is fine. but we have AI guideline: https://discourse.openrobotics.org/t/guidelines-for-ai-assisted-contributions-in-the-ros-project/55903 and please use our PR template to disclose the AI tools.

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.

[ros2lifecycle] set verb help message doesnt give enough information

2 participants