Here's some materials on doing atomic commits. As a follow-up for #6, read them when you have time:
- https://dev.to/cbillowes/why-i-create-atomic-commits-in-git-kfi
- https://curiousprogrammer.io/blog/why-i-create-atomic-commits-in-git
- https://curiousprogrammer.io/blog/how-to-craft-your-changes-into-small-atomic-commits-using-git
- https://frederickvanbrabant.com/posts/atomic-commits
- http://www.pauline-vos.nl/atomic-commits/
- https://www.codewithjason.com/atomic-commits-testing/
- https://fnune.com/2018/02/19/git-best-practices-atomic-commits/
- https://www.freshconsulting.com/insights/blog/atomic-commits/
- https://seesparkbox.com/foundry/atomic_commits_with_git
- http://adopteungit.fr/en/methodology/2017/04/26/how-to-do-atomic-commits.html
- https://zachholman.com/posts/git-commit-history/
- https://stackoverflow.com/a/38155649/595220
- https://git-rebase.io/
- https://css-tricks.com/creating-the-perfect-commit-in-git/
- https://www.simplethread.com/what-makes-a-good-git-commit/
- https://gist.github.com/efischer19/5d05178edd20054b3a9d85bd656f54f2