[x] Encapsulate a set of related changes in one commit (Make it easier to undo specific changes later)
[x] Concise commit messages (keep to the character limit)
[x] Focus on why a certain change was made
[x] Mention issue numbers (preview / link to chapter on issues)
These are just the ones that come to my mind immediately. There's probably tons of advice online.
We should keep it short, explain why this is a best practice and focus on things that readers with no experience can understand / appreciate after reading until that chapter (we can however reference future chapters, e.g., the point about linking to issues)
These are just the ones that come to my mind immediately. There's probably tons of advice online. We should keep it short, explain why this is a best practice and focus on things that readers with no experience can understand / appreciate after reading until that chapter (we can however reference future chapters, e.g., the point about linking to issues)