| ... | ... | @@ -4,6 +4,12 @@ |
|
|
|
|
|
|
|
These guidelines are there to facilitate working together on the same project. They are of course subject to change, but should lead to a more consistent development experience.
|
|
|
|
|
|
|
|
# Coding Style Guidelines
|
|
|
|
|
|
|
|
The repository contains a .clang-format file that defines the coding style. This style is enforced by a pipeline running on every merge request, rejecting it when the conditions are not met.
|
|
|
|
|
|
|
|
You can use clang-format directly on your code, or set up your IDE to format your code automatically.
|
|
|
|
|
|
|
|
# Commit Guidelines
|
|
|
|
|
|
|
|
General commit best practices apply. The main important thing is to encapsulate your commits to a **single purpose**. Do not to mix two features into one commit. Avoid mega commits, and keep them as concise and small as possible!
|
| ... | ... | |
| ... | ... | |
