Or you could refrain from the dogmatic commit style that serves literally zero purpose because in any healthy software project nobody is ever reading the commit history like that.
History and good explanations of what was changed and why is incredibly useful for being able to determine if something is a bug, a feature, and why something was written a particular way.
I’m not super stringent on commit style, but it absolutely helps to structure commit messages, especially in larger projects where they’re being worked on piecemeal.
Or you could refrain from the dogmatic commit style that serves literally zero purpose because in any healthy software project nobody is ever reading the commit history like that.
it looks cool and I can get back to developing software I abandoned when I have a better commit history
History and good explanations of what was changed and why is incredibly useful for being able to determine if something is a bug, a feature, and why something was written a particular way.
I’m not super stringent on commit style, but it absolutely helps to structure commit messages, especially in larger projects where they’re being worked on piecemeal.