commit 25229a77922f83690bc9c7cca913a0981ebc8716
parent 7225e59419034430eb595b66bdeb0ac0730dba43
Author: Eamon Caddigan <eamon.caddigan@gmail.com>
Date: Sat, 16 Nov 2024 15:30:47 -0800
Add a link and fix a typo
See? I did it right there!
Diffstat:
1 file changed, 13 insertions(+), 2 deletions(-)
diff --git a/content/posts/git-links/index.md b/content/posts/git-links/index.md
@@ -1,9 +1,10 @@
---
title: "Useful and interesting Git posts"
date: 2024-02-11T20:00:20-08:00
+lastmod: 2024-11-16T15:28:48-08:00
draft: false
categories:
-- Programing
+- Programming
tags:
- Git
---
@@ -58,4 +59,14 @@ things](https://matklad.github.io/2023/12/31/git-things.html)
about CI and code review is always fascinating to me---a “solo
developer”---a window into a whole other world of writing code for a living.
The tips for working on merge commits are great, and I’ve adopted Alex’s
-advice on moving files and starting with empty commits.
+advice on moving files and starting with empty commits
+
+[Chris Beams --- How to Write a Git Commit
+Message](https://cbea.ms/git-commit/)
+
+I can’t endorse any of Chris’s cryptocurrency advice, but this is the best
+post on why and how to craft commit messages. This post introduced me to the
+[use of the imperative mood](https://cbea.ms/git-commit/#imperative) for
+commit subjects. I.e., “a properly formed Git commit subject line should
+always be able to complete the following sentence: ‘If applied, this commit
+will _your subject line here_’.”