Another good resource I always point my developers to: https://chris.beams.io/posts/git-commit/

As someone who manages many codebases this combined with thoughtful squashed commits allows me to (1) understand at a high level what each commit does, (2) drill into each commit should I choose to in order to review what was done in more detail, and (3) review a JIRA ticket relevant to the change (which often times is more valuable than 1 and 2).