PastelKeystone comments on Git Commit Message

[–] PastelKeystone@lemmy.world 7 points 1 year ago (3 children)

Love it.

While folks are thinking about git commit messages I will offer this.

https://cbea.ms/git-commit/

My only criticism of the essay is that the most important bit is listed at number 7.

permalink

fedilink

source

hideshow 3 child comments

[–] merc@sh.itjust.works 2 points 1 year ago (2 children)

See also semantic commit messages where you tag every commit with the type of commit: feature, fix, docs, refactor, test, etc.

My only beef with it is that they chose "feat" as a way to shorten the word "feature" when "feat" is already a word that means something different. Not every feature is a feat, and a lot of the biggest feats are actually bug fixes.

permalink

fedilink

source

parent

hideshow 2 child comments

[–] PastelKeystone@lemmy.world 1 point 1 year ago (1 child)

I’ve seen semantic commits done with emojis which is cute but also annoying, because they’re not as easy to type or grep for.

Semantic commits can be nice, but they can also invite bikeshedding about what’s a “feature” and what’s a “bug fix”, etc.

Not saying they aren’t nice, and if folks are using them and liking them, keep going. But if you haven’t used them before on a team, then just be aware that’s a thing than can happen.

permalink

fedilink

source

parent

hideshow 1 child comment

[–] merc@sh.itjust.works 1 point 1 year ago

I'd rather have bikeshedding over terminology that eventually results in a single word than just have free-form commits where you can never tell what the primary motivation between a commit is.

permalink

fedilink

source

parent