From 96453177b9cbb79ecb5b2b98d05442d39759b530 Mon Sep 17 00:00:00 2001 From: Simon Michael Date: Mon, 4 Nov 2019 11:43:58 -0800 Subject: [PATCH] ;doc: contributing: commit message conventions aren't mandatory [ci skip] --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 3c57f9155..cb69648a3 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -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)