Thank you for writing this in such detail. It's a topic that has interested me throughout my career and I ended up using the ideas
explained at conventionalcommits.org.
In short, it's a few patterns and guidelines that make it easy for both humans and machines to read the git history. It allows you for example to generate changelog files automatically.
Front end developer specialising in JavaScript and React. Experienced in all aspects of modern front end development. Passionate about making accessible, secure and performant software.
Agreed. This is my goto as well. I find it much easier for consistently structuring commit messages and also the easiest way to understand what was done, especially in a large codebase.
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.
Thank you for writing this in such detail. It's a topic that has interested me throughout my career and I ended up using the ideas
explained at conventionalcommits.org.
In short, it's a few patterns and guidelines that make it easy for both humans and machines to read the git history. It allows you for example to generate changelog files automatically.
Agreed. This is my goto as well. I find it much easier for consistently structuring commit messages and also the easiest way to understand what was done, especially in a large codebase.