- Use only standard lib methods shipped with the language
- Write readable, correct and simple code (Keep It Simple and Stupid)
- Comment incomprehensible code
- Comply with the Conventional Commit Messages Standard (in commits and pr's)
- Avoid merge commits (use rebase merging)
- Create an issue for the bug you want to fix or the feature that you want to add.
- Create your own fork on GitHub, then checkout your fork.
- Write your code in your local copy. It's good practice to create a branch for each new issue you work on, although not compulsory.
- To run the test suite:
make build
to check if cpak still compilesmake test/unit
for unit testsmake test/cli
for testing cli commands.
- If the tests pass, you can commit your changes to your fork and then create
a pull request from there. Make sure to reference your issue from the pull
request comments by including the issue number e.g.
#123
.