News for hackers. Stuff that matters.
Re:Conventional Commits: A specification for structured comm... by jackcodes on Tuesday October 01, 2019 @10:21PM (#21132927)
Why don’t they put the additional information in the body of the commit?

I see this in nearly every company I go to - everyone rushing to skip over adding anything useful to the permanent log by using git commit -m rather than a plain got commit.

Re:Conventional Commits: A specification for structured comm... by _asummers on Tuesday October 01, 2019 @10:25PM (#21132947)
This is the place where (mentioned elsewhere in this thread) things like issue tracker links and other context can and _should_ go if you're using something like CC.
Re:Conventional Commits: A specification for structured comm... by AndrewHampton on Wednesday October 02, 2019 @10:57AM (#21137143)
Oh, we do. We are generally pretty great at filling in good details in the body. I didn't mention that originally because I didn't think it was noteworthy.

The main problem is very commit titles that end up looking like:

  feat(SomeScope.OtherScope.Class): add support for abc and xyz option