f314 comments on What's your commit message style?

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

submitted 3 years 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".

[–] f314@lemm.ee 37 points 3 years ago (3 children)

Conventional commits all the way! Even if I don’t use the keywords (feat, fix, etc.) I always write the comment in imperative tense; the message should tell you what happens if you merge it.

permalink

fedilink

source

hideshow 3 child comments

[–] hallettj@beehaw.org 7 points 3 years ago*

I totally agree.

Right now I'm on a new project with a teammate who likes to rebase PR branches, and merge with merge commits to "record a clean history of development". It's not quite compatible with the atomic-change philosophy of conventional commits. I'm thinking about making a case to change style, but I've already failed to argue the problem of disruption when rebasing PR branches.

permalink

fedilink

source

parent

[–] bloopernova@infosec.pub 6 points 3 years ago

Enforced by pre-commit, conventional commits has cleaned up our commit logs and changelog so much.

permalink

fedilink

source

parent

[–] key@lemmy.keychat.org 5 points 3 years ago

That's pretty neat. Is there a forked version that adds ticket number as a mandatory first class citizen? Cause that'd be darn near perfect.

permalink

fedilink

source

parent