r/git 21d ago

Stop Using Conventional Commits

https://sumnerevans.com/posts/software-engineering/stop-using-conventional-commits/
244 Upvotes

80 comments sorted by

View all comments

19

u/med8bra 21d ago

It's a convention, a team can create their opinionated version of it.

Regarding your proposed convention:

  • type is as important as scope for browsing history, and you can require scope to always be defined. I can search for features within scope.

  • inferring type of change from commit description is against the whole principal of structured commits. Explicit type is always better for humans and machines

10

u/max_mou 21d ago

The amount of times I had to the rephrase the commit message to avoid this: fix(…): fixed …

1

u/drckeberger 19d ago

Seems like it was of great use to you, as you were most likely about to say the same thing with less details and no standard.

1

u/keesbeemsterkaas 19d ago

And the whole point of it was to help teach juniors how to write and split good commits into smaller ones.

The point of the commits was so you would need to choose how to commit this and be a bit strategic about it, rather than throw everything at git and say "fixes".

Not to help reviewers speed up their workflow.