-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs(CONTRIBUTING): Improve the commit message documentation #1159
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As we just had the discussion, should we also add that links to issues should be done in the commit, not in the PR?
Add more details about the conventional commit types, the handling of breaking changes, and the versioning of the project. Fixes #319. Signed-off-by: Martin Nonnenmacher <martin.nonnenmacher@bosch.com>
Signed-off-by: Martin Nonnenmacher <martin.nonnenmacher@bosch.com>
Signed-off-by: Martin Nonnenmacher <martin.nonnenmacher@bosch.com>
b72ec7d
to
081922d
Compare
For example, use "Add feature" instead of "Added feature". | ||
#### Breaking changes | ||
|
||
Breaking changes should be indicated by either adding a `BREAKING CHANGE:` section to the commit message body or by adding a `!` after the type, for example: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We probably should communicate what is considered a breaking change, so is the REST API only thing we consider for versioning. Also, if we plan to do API versioning (/api/v1/
etc.) what exactly is a breaking change if we strictly follow that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add more details about the conventional commit types, the handling of breaking changes, and the versioning of the project.
Fixes #319.