There’s a community standard out there called Conventional Commit for structured git-commit messages. If you don’t know about it already, it recommends a strict type(scope?): description format for describing a code change in a repo.
I rarely read a comment I disagree with more than this, kudos.
In a typical 60 character space, you want to dedicate 5% of your oneline space to the chatacters “ure” so that you don’t mistake “feature” with the other words in english that start with “feat-”?
Yea, I don’t understand the reasoning behind that at all.
I rarely read a comment I disagree with more than this, kudos.
In a typical 60 character space, you want to dedicate 5% of your oneline space to the chatacters “ure” so that you don’t mistake “feature” with the other words in english that start with “feat-”?
Yea, I don’t understand the reasoning behind that at all.
Better idea, let’s get rid of all of the words and just say F: for feature, B: for bug fix
U do u my dude.