We welcome contributions in several forms, e.g.
- Documenting
- Testing
- Coding
- Reproducing Bugs
Please check Issues and look for unassigned ones or create a new one.
- Base pull requests on top of the latest
main
branch. - Pull requests must be rebased to the main branch before merging. We use fast-forward merges and squashing without creating merge commits to achieve a linear history.
- Follow our commit message style for the title and description of your pull request. This allows maintainers to use your title and description of the pull request as commit message.
- We tag releases on the main branch.
- CI checks must succeed before merging to
main
. - A maintainer listed in CODEOWNERS must review and merge the pull request.
We follow the commit message style of cbeams. The style in summary is:
- Separate subject from body with a blank line
- Limit the subject line to 50 characters
- Capitalize the subject line
- Do not end the subject line with a period
- Use the imperative mood in the subject line
- Wrap the body at 72 characters
- Use the body to explain what and why vs. how
Commit messages on pull requests can deviate from this style, because commits get squashed when merged to main
and maintainers can override the commit message.
However, give your pull request a subject and body in this style.
Commits on the main branch must follow this styleguide!
Commit messages must have a Signed-off-by
trailer certifying that the committer has the rights to submit the work under the project's license and agrees to the Developer Certificate of Origin
For filetypes not listed below follow the generic settings in .editorconfig
.
We follow the Ruff Formatter style, which is enforced in CI.
We use one line per sentence, and therefore don't enforce a maximum line-length for .md
files.
This keeps diffs cleaner and helps to quicker understand the structure of a paragraph when reading the raw .md
file.