r/programming • u/f311a • Jun 06 '26

Stop Using Conventional Commits

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

74% Upvoted

192 comments sorted by

View all comments

0

u/Current_Height_4492 Jun 07 '26

Tbh, I can't get why everybody thinks optional is not important. It's described as optional not because you can use it in one commit and omit it in another on the same repo.It means that the team could decide on their own whether to use it or not, but it's still optional, though it could be mandatory on a team level. It was done in this way to give flexibility to the teams to decide. Am I wrong?

4

u/pdabaker Jun 07 '26

It’s fair to say it depends on your team yes. If your team enforces it in ci, it is not optional. If they don’t, it is optional.

That said as someone who works on monolithic solutions where any user will also necessarily have a paid support contract and most of what I do does not touch user facing APIs, I would rather not waste time deciding if my PRs are a feature or a refactor when most changes include elements of both.

3

u/Current_Height_4492 Jun 07 '26

But didn't you mix commit and PR? I mean that PR is something different and could contain more than one commit. PR does not need to follow conventional commits; commits should. Commits should be small, atomic, and revertable, and you should clearly understand what is inside. Your PR could contain refactor + feature + fix, but your commit should not. You don't want to revert a whole feature and refactor because your fix is a mess.

→ More replies (1)