Thanks for triggering a discussion on a topic that deserves it and is very important.
I find that this article would gain from being refactored from a "this is what good commit is" to "this is how I commit".
Many of the things it recommends are far from consensual or standard, as pointed out by several comments. Similarly, the examples lack several features which are often considered as required for good commit messages.
As a consequence I think it would be more helpful for young programmers and for the community if it took a less normative approach, and rather a more descriptive one.
You make a good point, I am one of those young developers and probably made the article name a little too "absolute" as in everyone does them this way, rather than implying that it's my understanding of them.
I'm curious too - if you don't mind, what features did I miss that would be considered required for good commit messages?
Thanks for the comment, I always appreciate constructive criticism & feedback!
I am glad that you are receiving my comment positively!
It would probably take a whole blog post to answer your question, but I guess what comes closest to my opinion is this: chris.beams.io/posts/git-commit/
Thanks for triggering a discussion on a topic that deserves it and is very important.
I find that this article would gain from being refactored from a "this is what good commit is" to "this is how I commit".
Many of the things it recommends are far from consensual or standard, as pointed out by several comments. Similarly, the examples lack several features which are often considered as required for good commit messages.
As a consequence I think it would be more helpful for young programmers and for the community if it took a less normative approach, and rather a more descriptive one.
You make a good point, I am one of those young developers and probably made the article name a little too "absolute" as in everyone does them this way, rather than implying that it's my understanding of them.
I'm curious too - if you don't mind, what features did I miss that would be considered required for good commit messages?
Thanks for the comment, I always appreciate constructive criticism & feedback!
I am glad that you are receiving my comment positively!
It would probably take a whole blog post to answer your question, but I guess what comes closest to my opinion is this: chris.beams.io/posts/git-commit/
Best of luck for the start of your career!
Thanks - and thank you for the link! That will be good reading, I appreciate it.