Skip to content
Browse files

;doc: contributing: commit message conventions aren't mandatory

[ci skip]
  • Loading branch information...
simonmichael committed Nov 4, 2019
1 parent 6b5026c commit 96453177b9cbb79ecb5b2b98d05442d39759b530
Showing with 1 addition and 1 deletion.
  1. +1 −1
@@ -615,7 +615,7 @@ so think about future developers trying to understand them, git bisect, etc.

Rebase your commits against latest master for easiest review. Especially if they start to conflict.

Some conventions we often use in commit messages:
We like to use some conventions in commit messages when it makes sense. These aren't mandatory, but appreciated:

- prepend a [component](#components) prefix, eg `cli: ` or `journal: `, for clarity and to help with changelog production
- prepend a semicolon (`;`) to indicate commits that need not be mentioned in changelogs/release notes (as in the Emacs project)

0 comments on commit 9645317

Please sign in to comment.
You can’t perform that action at this time.