Programming

13368 readers

1 users here now

All things programming and coding related. Subcommunity of Technology.

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 1 year ago

MODERATORS

alyaza@beehaw.org

Hexorg@beehaw.org

remington@beehaw.org

What's your commit message style? (lemmy.sdf.org)

submitted 1 year ago by MariaRomanov@lemmy.sdf.org to c/programming@beehaw.org

57 comments fedilink hide all child comments

Was digging through a project at work today where some guy in 2014 made 100+ commits in a single day and the only one that had a comment said "upgrading to v4.0".

you are viewing a single comment's thread
view the rest of the comments

[–] HairHeel@programming.dev 25 points 1 year ago (1 children)

You get two options.

Normally it’s a squashed commit of everything in a feature, with a commit message like:

[JIRA-1234] - Descriptive but Concise Name of Feature

But every now and then it’s multiple commits like:

quick fix
Ugh, fix typo
fuck fuck why doesn’t it work
Oh, I’m stupid

[–] VanillaGorilla@kbin.social 12 points 1 year ago (1 children)

Followed by

fixed formatting

final formatting fix

you gotta be kidding me, fuck you, detekt!

[–] Elw@lemmy.sdf.org 6 points 1 year ago (2 children)

Bro, squash merge

[–] VanillaGorilla@kbin.social 3 points 1 year ago

Sure, but before squashing you gotta commit

[–] beardedrhino@lemmy.ca 3 points 1 year ago

Or if you're using feature branches, rebase, squash, and force push before opening the MR