Re:Commit messages guide
by tuxxy on Saturday April 20, 2019 @12:44AM
(#19704847)
Imperative makes way more sense when you're a maintainer and for people forking, etc.
When I merge changes from someone, the commits are always imperative. If there are two approaches taken, say "Use <method a> to foobar" and "Use <method b> to foobar", then the imperative case makes way more sense.
From my perspective, picking a commit to my preferred method is very wonky when it says, "Used <method a> to foobar".
When I merge changes from someone, the commits are always imperative. If there are two approaches taken, say "Use <method a> to foobar" and "Use <method b> to foobar", then the imperative case makes way more sense.
From my perspective, picking a commit to my preferred method is very wonky when it says, "Used <method a> to foobar".