Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README.md with lifecylce node info and fix minor typos #28

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

maverick-g00se
Copy link

@maverick-g00se maverick-g00se commented Apr 1, 2024

Bug fix

Fixed bug

As per the suggestion/request in the comments by @Yadunund from issue: #15

Note: PR #19 does attempt to solve the aforementioned as well. However, that PR has been left idle for over 2 weeks so I thought I might give it a whirl :)

Fix applied

Added extra lifecycle node information to the README.md and fixed some other minor typos accordingly as well.

@maverick-g00se maverick-g00se force-pushed the branch-updateReadMeWithLifecycleNode branch from b9efb95 to 93c4450 Compare April 1, 2024 13:03
…-off-by: maverick-g00se mavg00se@gmail.com

Signed-off-by: maverick-g00se <mvg00se@gmail.com>
@maverick-g00se maverick-g00se force-pushed the branch-updateReadMeWithLifecycleNode branch from 93c4450 to c2cc2c6 Compare April 1, 2024 13:23
Signed-off-by: maverick-g00se <mvg00se@gmail.com>
@Yadunund
Copy link
Member

Yadunund commented Apr 2, 2024

Thanks for the PR. There seems to be some overlap with #19 and since that PR was opened first, we should build off that to attribute changes to the author.

@maverick-g00se
Copy link
Author

Hey @Yadunund, Hope all is well! It has been about 3 months and PR #19 has stagnated. I'm just wondering since the aforementioned PR has dropped off, if we can move forward with this PR instead. Thanks!

@Yadunund
Copy link
Member

@maverick-g00se thanks for the ping. I've merged #19. Could your rebase this PR before we merge it in?

Signed-off-by: maverick-g00se <mvg00se@gmail.com>
@maverick-g00se
Copy link
Author

@Yadunund, I have just resolved the existing conflicts :)

README.md Outdated
@@ -1,16 +1,18 @@
# rmf_obstacle_detectors

Copy link
Member

Choose a reason for hiding this comment

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

I'd prefer not adding a newline after each heading. Same thing for other changes below where a newline is added before a codeblock.

Copy link
Author

Choose a reason for hiding this comment

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

oops, the auto formatter from work was on. I have fixed them as required. Thanks!

@Yadunund
Copy link
Member

Can you ensure your commits are signed so that DCO check passes?
https://github.com/open-rmf/rmf_obstacle/pull/28/checks?check_run_id=27898472404

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.

2 participants