3 ms·
Like the sibling comment, this comment reads like a person who don't realise the breath of projects git are used for. Not answering questions from my colleague
by madsbuch 3y ago
Like the sibling comment, this comment reads like a person who don't realise the breath of projects git are used for.
Not answering questions from my colleagues? No nee to be snarky, lets keep a good tone here.
Small refactorings is a good example of some code I would not write long commit messages. Like going through a function improving its clarity and adding comments – I would not redo that effort in the commit message. Text updates, style updates, etc. are also things that rarely merits big messages.
Great for you that you don't make 100 commits a day – but watch out that you don't mix disparate changes into a single commit.
- palata 3y ago> Not answering questions from my colleagues? No nee to be snarky, lets keep a good tone here. I didn't mean to be snarky, sorry if I read like that! I was trying to list examples of "non-coding" that I find are important :-). > Small refactorings is a good example of some code I would not write long commit messages. I totally agree! Now I am starting to think that we all agree here. I was just confused because your comment seemed to disagree with its parent, which says: "Sometimes that context fits in the subject line. For others, I expect an elaborate body". But apparently you do agree with that: sometimes it is worth writing a long commit message, sometimes it is not. It depends on the situation, and then it's a matter of common sense/experience.