This is pretty much how I've been doing commit messages for the past couple years, since adopting conventional commits and using standard version.
The only difference is my format is like this: [type]([scope]): [Subject].
and then the optional body, which generally only gets filled out if it's a very large commit (usually a no-no) or is filled in automatically by github on squash & merge of a PR, or if there's a breaking change.
So for example: feat(Foo): Adds the ability to bar.
fix(Bar): Bar should not prevent Foo.
BREAKING CHANGE: Bar now requires Baz.
Standard Version ingests these commits and automatically compiles a changelog, which we use as part of our deploy process. Result is an automagic changelog created on each production deploy that definitively captures all changes since the last deploy. It's glorious... and simple once you put the pieces in place.
The benefit of the scope being included is it will group all items by scope, alphabetically, in the changelog, and prefix each of the bulletpoints with that scope value so they're easy to spot.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is pretty much how I've been doing commit messages for the past couple years, since adopting conventional commits and using standard version.
The only difference is my format is like this:
[type]([scope]): [Subject].and then the optional body, which generally only gets filled out if it's a very large commit (usually a no-no) or is filled in automatically by github on squash & merge of a PR, or if there's a breaking change.
So for example:
feat(Foo): Adds the ability to bar.Standard Version ingests these commits and automatically compiles a changelog, which we use as part of our deploy process. Result is an automagic changelog created on each production deploy that definitively captures all changes since the last deploy. It's glorious... and simple once you put the pieces in place.
The benefit of the
scopebeing included is it will group all items by scope, alphabetically, in the changelog, and prefix each of the bulletpoints with that scope value so they're easy to spot.