From 4936224263dcbb3e27671d3f88c7b558813f9575 Mon Sep 17 00:00:00 2001
From: Alen <alen@dotfiles.xyz>
Date: Sat, 9 Sep 2023 16:37:16 +0400
Subject: Add .gitconfig

---
 dot_gittemplates/commit | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 dot_gittemplates/commit

(limited to 'dot_gittemplates')

diff --git a/dot_gittemplates/commit b/dot_gittemplates/commit
new file mode 100644
index 0000000..7f78cf8
--- /dev/null
+++ b/dot_gittemplates/commit
@@ -0,0 +1,17 @@
+
+# How to Write a Git Commit Message (https://cbea.ms/git-commit/)
+#
+# 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>
+#
+# [Add/Fix/Remove/Update/Refactor/Document/Style]: [issue #id] [summary]
+#
+# The seven rules of a great Git commit message
+#   1. Separate subject from body with a blank line
+#   2. Limit the subject line to 50 characters
+#   3. Capitalize the subject line
+#   4. Do not end the subject line with a period
+#   5. Use the imperative mood in the subject line
+#   6. Wrap the body at 72 characters
+#   7. Use the body to explain what and why vs. how
-- 
cgit 1.4.1-2-gfad0