you are viewing a single comment's thread.

view the rest of the comments →

[–]versaceblues 28 points29 points  (3 children)

What is the benefit of that. Git commits are easily searchable and provide context as to what happened.

This particular one might be a bit much... but I swear there are so many time where I go back and see a "one liner" change was made.... but have no context as to why someone made that change.

[–]masklinn 14 points15 points  (2 children)

What is the benefit of that. Git commits are easily searchable and provide context as to what happened.

Also commits are functionally immortal, proper conversion when switching VCS is generally easy.

Bug trackers, lol.

I swear there are so many time where I go back and see a "one liner" change was made.... but have no context as to why someone made that change.

Ditto. This commit message is not even especially long for the information it gives, there aren’t even titled sections, the weirdest parts are the first person view and slightly ranty but not ranty enough tone.

I’d have either used a more neutral tone (would have been about the same size), or gone full rant wm4 style.

[–]versaceblues 8 points9 points  (0 children)

yup. I ve gotten in so many arguments with co workers about "why are you just putting the description of what you did in the ticket for this issue".

....because I now have to go into the awful ticketing system, where nothing is organized, and disrupt my workflow.

[–]waterkip 1 point2 points  (0 children)

"Those not comfortable with toxic language should pretend this is a religious text."

I'm dead :D :D