Skip to content

Add notice to the ROS 2 and RTI Connext documentation (backport #227)#229

Open
mergify[bot] wants to merge 1 commit into
kiltedfrom
mergify/bp/kilted/pr-227
Open

Add notice to the ROS 2 and RTI Connext documentation (backport #227)#229
mergify[bot] wants to merge 1 commit into
kiltedfrom
mergify/bp/kilted/pr-227

Conversation

@mergify
Copy link
Copy Markdown

@mergify mergify Bot commented May 4, 2026

Description

Add notice about official ROS 2 and RTI Connext documentation to the README.

Is this user-facing behavior change?

Users will now have a direct link to the official ROS 2 and RTI Connext documentation in the README, with the most up-to-date information.

Did you use Generative AI?

No

Additional Information


This is an automatic backport of pull request #227 done by [Mergify](https://mergify.com).

Signed-off-by: Francisco Gallego Salido <fgallego@rti.com>
(cherry picked from commit 3dbef7c)

# Conflicts:
#	README.md
@mergify mergify Bot added the conflicts label May 4, 2026
@mergify
Copy link
Copy Markdown
Author

mergify Bot commented May 4, 2026

Cherry-pick of 3dbef7c has failed:

On branch mergify/bp/kilted/pr-227
Your branch is up to date with 'origin/kilted'.

You are currently cherry-picking commit 3dbef7c.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   README.md

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

Copy link
Copy Markdown
Contributor

@ahcorde ahcorde left a comment

Choose a reason for hiding this comment

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

@fgallegosalido do you mind to fix the conflicts ?

Copy link
Copy Markdown
Collaborator

@fujitatomoya fujitatomoya left a comment

Choose a reason for hiding this comment

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

@fgallegosalido does this need to backport to kilted?

@fgallegosalido
Copy link
Copy Markdown
Collaborator

@fujitatomoya yes. The documentation referenced starts at Kilted, so having the notice in the kilted branch can be really helpful for users that come by. I'll fix the conflicts as soon as possible.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants