3di | Triaging and reporting an issue

[keithkirkwood-3di]

Description

Refactor/consolidation and partial rewrite of content from several sources to create new articles for Triaging an issue, and Reporting an issue under Contributing section.

Related to: #6828

Did you use Generative AI?

No

Additional Information

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

[keithkirkwood-3di]

@kscottz @tfoote Hello - I've had an odd linter failure in this PR. Doesn't look like anything to do with my updates (I think). Could you advise on what I should do here?

[fujitatomoya]

i have a couple of minor comments on this PR.

i do understand that this PR is trying to restructure the tree but it would be nice to fix at the same time. btw, my comments should not block this PR.

[kscottz]

This is a good start but there's probably some more context that we could provide to make it better. Since this is geared towards new users there's a couple of things that we're failing to mention / cross reference in the documentation, including:

• How to figure out what ROS package is causing the issue and where to find that package's source code repository.
• How to use ros2 doctor to report your system configuration.
• As @fujitatomoya mentioned, how to use the report template.
• Where to find the appropriate log files in ROS.

Comments resolved and Kat's reviewed after. Keeping things moving we can iterate on it again.

[tfoote]

@mergify queue

[mergify]

Merge Queue Status

• 🟠 Waiting for queue conditions
• ⏳ Enter queue
• ⏳ Run checks
• ⏳ Merge

Waiting for

• -closed [📌 queue requirement]

All conditions

• -closed [📌 queue requirement]
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• any of [📌 queue -> configuration change requirements]:
  • -mergify-configuration-changed
  • check-success = Configuration changed
• any of [🔀 queue conditions]:
  • all of [📌 queue conditions of queue rule default]:
    • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
    • github-require-last-push-approval [🛡 GitHub branch protection]
    • github-review-approved [🛡 GitHub branch protection]
    • any of [🛡 GitHub branch protection]:
      • check-success = build
      • check-neutral = build
      • check-skipped = build
    • any of [🛡 GitHub branch protection]:
      • check-success = lint
      • check-neutral = lint
      • check-skipped = lint
    • any of [🛡 GitHub branch protection]:
      • check-success = test
      • check-neutral = test
      • check-skipped = test

[tfoote]

@mergify backport lyrical

[mergify]

backport lyrical

❌ No backport have been created

Details

• Backport to branch lyrical failed

Git reported the following error:

To https://github.com/ros2/ros2_documentation
 ! [rejected]        mergify/bp/lyrical/pr-6901 -> mergify/bp/lyrical/pr-6901 (fetch first)
error: failed to push some refs to 'https://github.com/ros2/ros2_documentation'
hint: Updates were rejected because the remote contains work that you do not
hint: have locally. This is usually caused by another repository pushing to
hint: the same ref. If you want to integrate the remote changes, use
hint: 'git pull' before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

[fujitatomoya]

@keithkirkwood-3di can you resolve the conflicts in the backport PRs? or are we not backporting those fixes to downstream branches?

[fujitatomoya]

@keithkirkwood-3di can you resolve the conflicts in the backport PRs? or are we not backporting those fixes to downstream branches?

i guess we are already doing this, see #7031