1
0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00
RIOT/CONTRIBUTING.md
Ludwig Ortmann 61f405edaa Update CONTRIBUTING.md
Add comment about labels, hint at Development Procedures.
2014-07-11 09:20:58 +02:00

15 lines
895 B
Markdown

# CONTRIBUTE
This is a short version of the [Development Procedures](https://github.com/RIOT-OS/RIOT/wiki/Development-procedures).
1. Check if your code follows the [coding conventions](https://github.com/RIOT-OS/RIOT/wiki/Coding-conventions). If the code does not comply these style rules, your code will not be merged.
2. The master branch should always be in a working state. The RIOT maintainers will create release tags based on this branch, whenever a milestone is completed.
3. Comments on a pull request should be added to the request itself, and *not* to the commit.
4. Keep commits to the point, e.g., don't add whitespace/typo fixes to other code changes. If changes are layered, layer the patches.
5. Describe the technical detail of the change(s) as specific as possible.
6. Use [Labels](https://github.com/RIOT-OS/RIOT/wiki/Labels) to help classify pull requests and issues.