From 6c9f50a2d52a8aead2ef5a59ae503a712173b75a Mon Sep 17 00:00:00 2001 From: Simon Michael Date: Mon, 15 Jul 2019 17:52:17 +0100 Subject: [PATCH] ;doc: contrib: wording [ci skip] --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 4bab849dd..7b595edcd 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -622,8 +622,8 @@ Rebase your commits against latest master for easiest review. Especially if they Some conventions we often use in commit messages: - prepend a [component](#components) prefix, eg `cli: ` or `journal: `, for clarity and to help with changelog production -- prepend a semicolon (`;`) to indicate boring commits that won't affect changelogs/release notes (as in the Emacs project) -- add a final `[ci skip]` line for commits which probably don't need to trigger a CI build, to reduce carbon emissions from Travis +- prepend a semicolon (`;`) to indicate commits that need not be mentioned in changelogs/release notes (as in the Emacs project) +- append a final `[ci skip]` line to indicate commits that need not trigger a CI build, to reduce carbon emissions from Travis. ### The docs