Add NAMESPACE support to ament_export_targets (backport #498)#505
Merged
Add NAMESPACE support to ament_export_targets (backport #498)#505
Conversation
* Add NAMESPACE support to ament_export_targets * Improve documentation for NAMESPACE argument Signed-off-by: Ryan Friedman <ryanfriedman5410+github@gmail.com> (cherry picked from commit 7fdd2d1)
Contributor
|
Contributor
|
This time with correct ros2.repos:
|
Contributor
|
DCO is being weird: |
Contributor
Yeah, it is always weird on backports because the Signed-off-by line isn't where it is expecting it. I'll just mark it as fine. |
mjcarroll
approved these changes
Feb 23, 2024
Contributor
|
Can a maintainer do a release on |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is an automatic backport of pull request #498 done by Mergify.
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill merge the base branch into this PR@Mergifyio backport <destination>will backport this PR on<destination>branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com