Thank you for your interest and time spent contributing!
We welcome contributions from everyone, and to ensure our community stays open and healthy
we adhere to the Contributor Covenant, a widely
used code of conduct adopted by many other communities such as
Linux, Autoware, GitLab.
First, please read through our code of conduct, as we expect all our contributors to follow it.
Second, before starting on a project that you intend to contribute to any of our
projects, we strongly recommend posting on the repository's
Issues page or
Discord and
briefly outlining the changes you plan to make.
This will enable us to provide
some context that may be helpful for you. This could range from advice and
feedback on how to optimally perform your changes or reasons for not doing it.
- Create an issue or post on Discord defining your intended contribution
- Create a fork
- For more information about the fork-and-pull model, see the GitHub Docs.
- Write code
- Create a pull request
- Fill the template
- For more information about the fork-and-pull model, see the GitHub Docs.
- Finish a pull request
- In order for a pull request to be merged to mini_pupper_bsp, it must meet the following criteria:
- All discussions on the pull request must be resolved.
- All items of the pull request checklist are checked off.
- CI jobs for the pull request must have passed successfully.
- In order for a pull request to be merged to mini_pupper_bsp, it must meet the following criteria:
For Pull Requests, please target the main
branch for any contributions.
To contribute, please check out the main
branch, and then create your feature
branch from there:
git checkout main # start with the main branch
git pull origin main # pull remote repo changes
git checkout your-feature-branch # create your feature branch
Then when you submit a Pull Request, please select the main
branch to request
to merge your commits.
If you are interested in understanding this development style a bit further, we follow the GitHub Flow model of branching.