How To Write A Commit Message

tl;dr: Guideline is "write a concise message, starting with a capitalized verb in the root form, explaining what you did to the code and what the code does to the software."

featured in #161

Highlights From Git 2.24

- Taylor Blau tl;dr: With features and bug fixes from over 78 contributors, 21 of them new. A look at some of the most exciting features and changes introduced since Git 2.23

featured in #160

How To Write Useful Commit Messages (My Commit Message Template)

- Jacob Herrington tl;dr: A good message should be able to allow the readers to understand (1) what was done at a glance (2) why the change was necessary (3) the details about what was done (4) any useful details concerning the change. You can see the template here.

featured in #156

Git Is Eating The World

- Jan van den Berg tl;dr: Git dominates the DVCS market. Yet Bitbucket's announcement that it will sunset support for Mercurial - a Git rival - caused a stir. It emphasizes Git's dominance and lack of competition.

featured in #151

Oh Shit, Git!

- Katie Sylor-Miller tl;dr: At times, it's not easy to untangle yourself from git. Here's a few situations the author has gotten herself into and how she fixed them "in plain English."

featured in #138

15 Git Commands You May Not Know

- Zaiste tl;dr: List of 15 Git commands that you may not know. The author also recommends trying Magit, an interface to Git implemented as an Emacs package.

featured in #137