3 ms·

Speaking of Git commit messages, it's worth pointing out this wiki[1], written and reviewed by some long time open source contributors. It's a bit verbose, but

Speaking of Git commit messages, it's worth pointing out this wiki[1], written and reviewed by some long time open source contributors. It's a bit verbose, but rewarding to the patient reader. On writing Git commit subject lines, I've come to appreciate why the imperative mood is nicer (as opposed to the and indicative mood). Some related reasoning here[2]. [1] https://wiki.openstack.org/wiki/GitCommitMessages https://wiki.openstack.org/wiki/GitCommitMessages [2] http://chris.beams.io/posts/git-commit/ http://chris.beams.io/posts/git-commit/

js2 11y ago
Add comment strongly agreeing with parent The links in the parent comment are to documents which are prescriptive, based on hard-earned experience, and provide well-reasoned justifications for how and why to format commit messages, along with examples of projects which do so. I wish the parent comment were at the top of the page, but I can provide only a single upvote. This comment is to provide more exposure than an upvote alone, and so that I can find it my HN history.
- gkya 11y ago
  - http://orgmode.org/ http://orgmode.org/ (or Evernote, this-pad, that-pad...) - https://en.wikipedia.org/wiki/Bookmark_%28World_Wide_Web%29 https://en.wikipedia.org/wiki/Bookmark_%28World_Wide_Web%29 - Direct link to parent comment: https://news.ycombinator.com/item?id=9764039 https://news.ycombinator.com/item?id=9764039