From ab244d2331a527eb12dbd05febd30ddb1b0b1cfc Mon Sep 17 00:00:00 2001
From: Adam Simpson <adam@heysparkbox.com>
Date: Thu, 27 May 2021 13:25:19 -0400
Subject: [PATCH] feat: document prompt for formatting good git-commit
 subjects.

---
 code-style/git/.gitmessage | 2 ++
 code-style/git/README.md   | 4 +++-
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/code-style/git/.gitmessage b/code-style/git/.gitmessage
index be88f66e..2cb6cd16 100644
--- a/code-style/git/.gitmessage
+++ b/code-style/git/.gitmessage
@@ -5,6 +5,8 @@
 #
 # <footer>
 #
+# ** A good message should complete this sentence: when applied, this commit will... **
+#
 # ** TYPES **
 # feat (new feature)
 # fix (bug fix)
diff --git a/code-style/git/README.md b/code-style/git/README.md
index 78ed4496..09fe3f3c 100644
--- a/code-style/git/README.md
+++ b/code-style/git/README.md
@@ -117,7 +117,8 @@ Find the [allowed types above](#Allowed-Values-for-Types).
 
 An [imperative tone][365] is also helpful in conveying what a commit does,
 rather than what it did. For example, use **change**, not _changed_ or
-_changes_.
+_changes_. To put it another way: a good subject should complete this sentence:
+["when applied, this commit will..."][drew-devault-link]
 
 ### Funtip
 
@@ -327,3 +328,4 @@ Voila! You're done. You've successfully rebased a branch onto the master branch!
 [example PR template]: ./PULL_REQUEST_TEMPLATE.md
 [example issue template]: ./ISSUE_TEMPLATE.md
 [Create a branch]: #naming-branches
+[drew-devault-link]: https://drewdevault.com/2019/02/25/Using-git-with-discipline.html