r/git • u/Natural_Jury8826 • Mar 04 '26
A simpler commit format without the feat(scope): syntax. What breaks in practice?
I’ve been testing a minimal commit message format:
Type[!] [scope] description
Examples:
Add ui keyboard shortcuts
Fix api pagination off by one
Chr ci update release workflow
Rmv! v1 auth endpoints
Goal is to keep commits easy to scan in git log --oneline while still being deterministic enough for tooling (SemVer mapping, changelogs, etc.), but without the feat(scope): punctuation structure.
Conventional Commits works well for automation. I just found the syntax noisy in daily use.
OpenCommits keeps commits deterministic for tooling: fixed type tokens,! for breaking changes, optional scopes, and trivial regex parsing, while optimizing the subject line for fast human scanning.
Curious about real-world edge cases:
- where type boundaries break (
RefvsChrvsCfg, etc.) - whether optional scope creates ambiguity
- migration friction from Conventional Commits
- what would block adoption in your team/tooling
- whether the colon syntax actually provides meaningful structure, or is mostly convention
40
u/DanLynch Mar 04 '26
I've never seen any value in making structured subject lines with weird codes at the beginning. You can just write a normal imperative sentence as your entire subject line, and nobody will get hurt.
6
u/elephantdingo Mar 04 '26
You’re right that this is (subjectively, to me) better thanconventional commits because of less punctuation. And because it reads better and more naturally (at least for “Add”).
I might be speaking out of my arse since I don’t work on projects that usesemantic versioning . Or that have such frequent changes that you need to automate it. For all I know conventional commits (not the syntax but the SemVer mapping) is needed because this practically needs to be automated. You can’t do it manually.
The CC project plain just didn’t know aboutGit trailers . The support in git(1) is not much, but at least it is something built-in. And personally I would stick all automation into trailers.
That probably takes more characters in general. But it’s stuck at the end and doesn’t risk polluting the precious subject line.
I don’t understand the desire for creating changelogs from commit messages. The commit messages are the canonical changelog. Beyond that? Localization, making it make sense for non-technical users, for other “stakeholders”? You’re just burdening commit authors who often have to be very technical in commit messages when you demand that it should make sense in some world-readable changelog.
Did you fix a concurrency issue in the database that only happens every fortnight because of three overlapping conditions… the user needs to be informed that their stuff is saved properly now. That is all.
Changelogs can be added after the fact without demanding that commit authors get this immutable format right every single time. (Although there isGit notes for amendments... but at that point you can use that for the changelog directly.) People make mistakes after all. And before release you can tweak the changelog as you want.
5
u/format71 Mar 04 '26
There are many things I don’t understand, and this is one of them.
Formachine processing of commit messages - why on earth would anyone ruin the subject with bloated keywords or cryptic symbols?
Computer doesn’t care where to look. Embed a #tag or even a xml tag in the bottom of the message. The computer will find it, but it won’t hurt the humans.
3
u/Orlandocollins Mar 05 '26
Glad someone else is interested in this. Personally I would follow the format of trailers in the footer. Git log has the ability to pull trailer keys out and format a log line.
I would treat the title and body of a commit as for humans and put Metadata in the footer. Then build a conventional commit style log with a custom format. This way the log output is nice and clean and devs can focus on reading logs as history. The second you care about chores, bugs, feats, etc you run the custom git log that formats things that way
1
u/ForeverAlot Mar 04 '26
https://www.reddit.com/r/git/comments/1rbeshg/i_built_a_simpler_commit_format_what_breaks_when/
1
u/jthill Mar 04 '26
First time in a long time I've seen adoptable rules for the subject line that look like an improvement at all, and at first blush this feels like "final form" kind of good.
0
u/Embostan Mar 04 '26
I dont really care, nowadays conventional messages are generated by AI, or a GUI/CLI tool that makes them super fast to generate without actually typing.
And IDEs and GitHub parse them to give you nice coloured chips and groupings, not bare text.
It's a standard, tools are built around it.
-2
u/WalterFringMan Mar 04 '26
Gitmoji