clober_msgs repository

Repository Summary

Checkout URI https://github.com/CLOBOT-Co-Ltd/clober_msgs.git
VCS Type git
VCS Version foxy-devel
Last Updated 2021-08-02
Dev Status DEVELOPED
CI status No Continuous Integration
Released UNRELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Packages

Name Version
clober_msgs 0.1.0

README

clober_msgs

Clober Robot Hardware Standard Messages

CONTRIBUTING

No CONTRIBUTING.md found.

Repository Summary

Checkout URI https://github.com/CLOBOT-Co-Ltd/clober_msgs.git
VCS Type git
VCS Version noetic-devel
Last Updated 2021-09-14
Dev Status DEVELOPED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Packages

Name Version
clober_msgs 1.0.1

README

clober_msgs

Clober Robot Hardware Standard Messages

CONTRIBUTING

Contributing to clobot

Thanks for your attention to clobot’s robot and open-source packages.

For more details about clober and RMF(Robotics Middleware Framework), read this documentation.

If you want to suggest an idea or make a better code for the robot, just sending your pull requests. But, please comply following rules.

License

By contributing, you agree that your contribution will be licensed under its Apache License.

Apach 2 License

https://www.apache.org/licenses/LICENSE-2.0

Coding Style

We adapt coding convention recommended from ROS1/ROS2, as follow as

If you want to contribute repositories forked from open-rmf repositories, please follow open-rmf coding convention. See this link

Commit/PR Message

Message template

type: title

 - write body 1
 - write body 2

close/fix/resolve #number_of_issue
related to #number_of_issue

You can configure the message template as following command git config --global commit.template /PATH/YOUR/.gitmessage

Rule

  • first of all, put 'type' of the commit message

|Type |Description| |:--- |:----------| |feat |New feature| |fix |bug fix| |docs |changes to documentation| |style |formatting, missing semi colons, etc / no code change| |refactor|refactoring production code| |chore |updating grunt tasks etc / no production code change|

  • And remember
    • Capitalize the subject line
    • Use the imperative mood in the subject line
    • Do not end the subject line with a period
    • Separate subject from body with a blank line
    • Use the body to explain what and why vs. how
    • Can use multiple lines with "-" for bullet points in body

Contact

Please contact on email : ros@clobot.co.kr