this post was submitted on 10 Oct 2024
1 points (53.8% liked)

JetBrains

140 readers
2 users here now

A community for discussion and news relating to JetBrains and its products! https://www.jetbrains.com/

Related Communities

Copyright ยฉ 2000-2024 JetBrains s.r.o. JetBrains and the JetBrains logo are registered trademarks of JetBrains s.r.o.

founded 9 months ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] heiglandreas@phpc.social 1 points 1 month ago (2 children)

@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@techhub.social 1 points 1 month ago (1 children)

@heiglandreas @ramsey @jetbrains how do you expect IntelliJ to support this? When if the second line isn't blank?

[โ€“] heiglandreas@phpc.social 1 points 1 month ago (1 children)
[โ€“] clovis@techhub.social 1 points 1 month ago

@heiglandreas @ramsey @jetbrains what's the problem then ๐Ÿ˜…

[โ€“] heiglandreas@phpc.social 1 points 1 month ago

@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