From 86ac4450714be8b8230e8e92575ef5bee72d44e2 Mon Sep 17 00:00:00 2001
From: Rune Philosof <57357936+runephilosof-abtion@users.noreply.github.com>
Date: Mon, 12 Jan 2026 11:20:22 +0100
Subject: [PATCH] Add commit messages documentation

Hopefully this will result in commit messages that are more valuable when you dig back in the code history.
---
 technical_practices/commit_messages.md | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 technical_practices/commit_messages.md

diff --git a/technical_practices/commit_messages.md b/technical_practices/commit_messages.md
new file mode 100644
index 00000000..694f5197
--- /dev/null
+++ b/technical_practices/commit_messages.md
@@ -0,0 +1,17 @@
+# Commit Messages
+
+The most important information in commit messages is *why* you made the change.
+
+Nice to have:
+
+* Summary of the changes (it helps when going back in history and trying to decide whether a change was accidentally added to commit).
+* Thoughts about decisions you made.
+* Links to Asana task, or other relevant info like a Github bug report, stackoverflow, etc.
+* Keep the headline less than 50 characters, if possible.
+
+https://www.freecodecamp.org/news/how-to-write-better-git-commit-messages/
+> To come up with thoughtful commits, consider the following:
+> * Why have I made these changes?
+> * What effect have my changes made?
+> * Why was the change needed?
+> * What are the changes in reference to?