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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
No prefixes is a lot less useful. Commits can provide structure and guidance.
Personally, I don't like
chorethough, and we don't use it in our project, reducing the number of types. Typically, those aremisc(proj)ormisc(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.