From 2ab69e081674596352f3fd4a2af874fad9abfdcf Mon Sep 17 00:00:00 2001 From: erikjohnston Date: Wed, 13 Dec 2023 15:42:43 +0000 Subject: deploy: 8613f7693ea284a023dc625c9a35b9ff482f5fd0 --- develop/development/git.html | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'develop/development/git.html') diff --git a/develop/development/git.html b/develop/development/git.html index 71ff726695..cd675a4207 100644 --- a/develop/development/git.html +++ b/develop/development/git.html @@ -124,10 +124,10 @@ - + - + @@ -168,10 +168,10 @@ before. Here, by way of an arbitrary example, is the top of git log --grap

Note how the commit comment explains clearly what is changing and why. Also note the absence of merge commits, as well as the absence of commits called things like (to pick a few culprits): -“pep8”, “fix broken +“pep8”, “fix broken test”, -“oops”, -“typo”, or “Who's +“oops”, +“typo”, or “Who's the president?”.

There are a number of reasons why keeping a clean commit history is a good thing:

-- cgit 1.5.1