From 72ad95650e8de41cbed609c232b6b9bb90264f25 Mon Sep 17 00:00:00 2001
From: Michele Cereda <cereda.michele@gmail.com>
Date: Fri, 17 Mar 2023 22:09:37 +0100
Subject: [PATCH] chore: added article for conventional commits and started
 using them

---
 knowledge base/conventional commits.md | 28 ++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)
 create mode 100644 knowledge base/conventional commits.md

diff --git a/knowledge base/conventional commits.md b/knowledge base/conventional commits.md
new file mode 100644
index 0000000..067eaaa
--- /dev/null
+++ b/knowledge base/conventional commits.md	
@@ -0,0 +1,28 @@
+# Conventional commits
+
+Lightweight convention on top of commit messages.<br/>
+It provides an easy set of rules for creating an explicit commit history.
+
+## Table of contents <!-- omit in toc -->
+
+1. [TL;DR](#tldr)
+1. [Further readings](#further-readings)
+
+## TL;DR
+
+A commit message should be structured as follows:
+
+```text
+<type>[optional scope]: <description>
+
+[optional body]
+
+[optional footer(s)]
+```
+
+## Further readings
+
+- [Website]
+
+<!-- project's references -->
+[website]: https://www.conventionalcommits.org