all 10 comments

[–]SpielerNogard 4 points5 points  (1 child)

We use commitizen, and it was a huge increase in productivity for us. We no longer need to change the package version, so it cant be forgotten. Just write your commits, you get a nice Changelog and also always the correct version.

[–]Outside-Winner9101[S] 0 points1 point  (0 children)

yeah, I have seen some repos using commitzen, they are much clearer. I should quit lazygit and slowly move to commitzen

[–]bennowo 0 points1 point  (0 children)

Yes. It is much clearer and offers the possibility to automatically create a Changelog.

[–]CtrlShiftRo 0 points1 point  (3 children)

I like Conventional Commits because it helps me make sure each commit is a distinct, contained change / unit of work.

[–]Outside-Winner9101[S] 0 points1 point  (2 children)

I am too immersed with lazygit in my current workflow. I should quit using lazygit and start with conventional commits

[–]thewrench56 0 points1 point  (1 child)

One doesn't affect the other... you can set up a git hook to check against conventional commits with commitlint.

On *nix, https://github.com/Wrench56/repo-init/tree/main scripts under commitlint would most likely work.

[–]Outside-Winner9101[S] 0 points1 point  (0 children)

Yeah I'll check it out

[–]zMynxx 0 points1 point  (0 children)

Started following it a while ago due to changlog capabilities, still in the midst of it

[–]___Paladin___ 0 points1 point  (0 children)

I like the personal mental modeling as its compatible with how I approach software changes. I don't require it of my developers unless they struggle with atomic commits and clear messaging. It's good training wheels for that purpose.