Git Commit Messages - Why keep the 50 character convention?
As developers, we should all know how to write a good git checkin message. Done right, it makes delving into change histories delightful rather than a chore. What's that? You have never been told how to write a good checkin message? Chris Beam's article is just the thing for you! (Chris explains the rules far better than I could here without going off on a tangent) TL;DR: Separate subject from body with a blank line Limit the subject line to 50 characters Capitalize the subject line Do not end the subject line with a period Use the imperative mood in the subject line Wrap the body at 72 characters Use the body to explain what and why vs. how But I want to talk about Rule #2 (with a little about Rule #6 thrown in). That 50 character first line limit. Rule 2. Limit the subject line to 50 characters Back in the Dark Ages, when monitors were typically 80 characters wide, this limit made some physical sense. You didn't want to wrap commit summaries because it makes them scra...