this post was submitted on 16 Nov 2026
7 points (81.8% liked)

Programming

29304 readers
559 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 3 years ago
MODERATORS
top 9 comments
sorted by: hot top controversial new old
[–] beyond@linkage.ds8.zone 1 points 24 minutes ago* (last edited 22 minutes ago)

My pet peeve with conventional commits is that some brain genius decided to shorten "feature" into "feat", a completely different word, in order to save three characters.

I suppose implementing a feature can be a feat sometimes.

[–] Kissaki@programming.dev 1 points 32 minutes ago

Resource links for your convenience

[–] atzanteol@sh.itjust.works 3 points 11 hours ago (4 children)

Fuck no. Stop trying to stuff data into commit messages. Just describe your change succinctly so I know what you did. This "feat" "fix" and "chore" bullshit needs to stop.

[–] Kissaki@programming.dev 1 points 36 minutes ago

I want to be able to scan a commit log, not just read commit titles one by one.

The type gives me a scoping of to be expected intention, change size, and potential for side effects. docs never have runtime side effects.

The scope gives me categories to scan for. Which area of the project am I searching for? Which product feature? If there's a user bug, I can check those in the specific area and more general ones first.

I need scope to be small, so the visual scanability is not broken because of horizontal shifting of the actual commit change title.

I made sure my team capitalizes the commit change title, as an additional visual queue for scanability; being able to blend out the prefix.

Even if you don't care about changelog generating or log scanability for developers searching, debugging, or analyzing, I find deliberate commit messages practice helpful in guiding both in thought and documenting though of what the intention of the commit is, whether to split changes because they're logically unrelated/not the same step, etc.

In a small project or freshly started project before going stable or sizable it may not be necessary, but I still enjoy following the general practice.

(cut off because it's a customer project, just to be sure)

No prefixes is a lot less useful. Commits can provide structure and guidance.

Personally, I don't like chore though, and we don't use it in our project, reducing the number of types. Typically, those are misc(proj) or misc(ci) instead.

The customer receives a list of feat and fix commit titles as info with a release.

Commits are already data. Metadata about changes. Merge commits are structured data, putting individual changes into structured context. Using short well defined prefixes/prefix formats is a logical extension.

[–] codeinabox@programming.dev 2 points 3 hours ago

How would you automate changelog generation and semantic versioning without conventional commits? For me, this is the biggest selling point of this standard, when paired with tools like Release Please.

[–] Tanoh@lemmy.world 1 points 3 hours ago

I always write just WIP or something simple. Commit often, so you can easily go back if you mess something up.

Then later when the branch gets merged, I squash it with a proper commit message (that no one will ever look at, but those are the rules!)

[–] thenextguy@lemmy.world 7 points 10 hours ago* (last edited 10 hours ago) (2 children)

The bigger problem by far in my experience is getting devs to write more than 'fixed bugs' or other meaningless drivel. Trying to get them to conform to any standard like this would be impossible unless enforced by some commit hook (dear god no!).

Even this new 'standard' shows the commit body as [optional]. The first line in a git commit is supposed to be a short summary, not the entire message. I try to write whole sentences, paragraphs and bullet lists in anything that isn't trivial.

My last job enforced a Jira ticket number looking thing, but didn't actually check that it was a valid ticket. The number of times I would read a commit message with zero content, then go to jira to find some reference and either find the wrong ticket, or perhaps the right ticket, but still no description, ... too damn high!

[–] The_Decryptor@aussie.zone 2 points 6 hours ago

I've seen people suggest using the inverted pyramid method style that journalists use.

https://en.wikipedia.org/wiki/Inverted_pyramid_(journalism)

Idea being that you front load the important stuff, so if you only read e.g. the first 5 lines, you don't miss anything important later on, you can only "refine" the information you've already received.

[–] atzanteol@sh.itjust.works 1 points 7 hours ago

Oddly enough the folks I work with are really good at the Jira ticket thing and frankly it's much more useful than "feat" prefixes on everything. Because the Jira ticket gives me a "why" which can be amazingly helpful when trying to figure out "why was this line added".

I have never once found feat/fix/chore to be of any use when looking at history. It's useless noise.