After seeing people use the @jetbrains UI to commit to git I understand where all those - sorry: shitty - commit messages come from…
🙈
An improvement would already be to have a “Subject” line and the text box.
And have the subject line follow the Beams Rule.
Sonthat the first line of the commit message finishes the sentence
“When this commit is applied it will…”
And please: No longer than 56(?) characters (Unicode). Keep it short. You got the textbox to explain *why* in full length.
@heiglandreas @ramsey @jetbrains see, that’s exactly *why* IntelliJ shouldn’t have a default opinion on this. Why wouldn’t they choose these conventions? They’re popular.
Instead they should have the safest possible default, and let you easily configure your own conventions. When possible, by reading git configuration for anything standard. Which is what IntelliJ already does.
@clovis
We might be talking about two different sets of standard. What I would want Jetbrains to support out of the box is the “Subject line, Blank Line, Body” convention that is recommended in the git docs.
People can happily change the defaults to whatever they want but the recommendation from git should IMO be the default.
/cc @ramsey @jetbrains
@clovis
Whether the users then use conventional commits, beams rule, opensavvy, whatever else they want is a completely different question.
And I am absolutely with you that Jetbrains should not favour one over the other.
/cc @ramsey @jetbrains
@heiglandreas @ramsey @jetbrains how do you expect IntelliJ to support this? When if the second line isn’t blank?
@clovis They already DO support it.
/cc @ramsey @jetbrains
@heiglandreas @ramsey @jetbrains what’s the problem then 😅