Recommended links about Git

Ship / Show / Ask [article]
Rouan Wilsenach shares a branching strategy which matches how I encourage many teams to work with pull requests
No code reviews by default [article]
Thomas Paul Mann offers some great advice on giving engineers responsibility for deciding when they want a code review for the changes that they have made
How to Do Code Reviews Like a Human [article]
Michael Lynch offers some really excellent advice in this two parter on giving code reviews
How to make your code reviewer fall in love with you [article]
Don't be put off by the title, this article is packed with great advice for making it easier for your colleagues to give you valuable feedback on your code.
Proof your thousand-line pull requests result in more bugs [article]
Tekin takes you through the evidence for bigger pull requests being more error prone and then gives some great advice for keeping them smaller
KonMari for your Git repositories [article]
A couple of useful git aliases for cleaning up your old branches
Getting more from Git [video]
Alice Bartlett provides great advice on good git commit practices far more clearly than I ever could with the added bonus of sharing some interesting notes on the history of git which gives you insight into why the UI for git is so poor
Simplify writing code with deliberate commits [video]
A talk by me about how good commit practices help you clear your head
A branch in time [video]
Tekin Süleyman tells an engaging story about the value of good commits
Intentional Git Commit Messages [article]
Steve Tarver makes the case for communicating the intent of your commits
Telling stories with your git history [article]
Seb Jacobs’s detailed write up of the practices that help you tell stories with your commits
Telling stories through your commits [video]
My talk about how good commit practices help you and your team mates in the long run
How to write a git commit message [article]
Chris Beams's excellent advice on commit messages
Every line of code is always documented [article]
Mislav Marohnić's guide to using git to reveal this documentation