From 23f0dbcd19c687c4e33a0908052dc92b5702d8b3 Mon Sep 17 00:00:00 2001 From: Edie Lemoine Date: Thu, 4 Jul 2024 11:49:04 +0200 Subject: [PATCH] docs: update developers.md --- DEVELOPERS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/DEVELOPERS.md b/DEVELOPERS.md index d156666b..fc6b7d68 100644 --- a/DEVELOPERS.md +++ b/DEVELOPERS.md @@ -40,11 +40,11 @@ Most of what is written in the specification is also explained in the following ### Rules - Use the imperative mood in the subject line. - - For example: "Fix bug" instead of "Fixed bug" or "Fixes bug". + - For example: "fix bug" instead of "fixed bug" or "fixes bug". - Do not capitalize the subject line. - Do not end the subject line with a period. - Use the body to explain the "what" and "why" of the commit, not the "how". - - For example: "This commit fixes a bug" instead of "This commit fixes a bug by changing the code in this way". + - For example: "this commit fixes a bug" instead of "this commit fixes a bug by changing the code in this way". - If the commit fixes an issue, add "Closes #issue-number" to the body. - In case there are multiple issues, add "Closes #issue-number, Closes #issue-number, ..." to the body.