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.
By contributing, you agree that your contribution will be licensed under its Apache License.
https://www.apache.org/licenses/LICENSE-2.0
We adapt coding convention recommended from ROS1/ROS2, as follow as
- http://wiki.ros.org/StyleGuide
- https://docs.ros.org/en/foxy/Contributing/Code-Style-Language-Versions.html
If you want to contribute repositories forked from open-rmf repositories, please follow open-rmf coding convention. See this link
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
- 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
Please contact on email : [email protected]