Recently there was an article on LinkedIn about how debugger statement was left in the production code (front end javascript) and thus user could not move forward.

People commented about the code review.

But why invest manual efforts when such things can be automated ? See #4 in the list below.

pre-commit hook is an under appreciated (dare I say, unknown) feature of git

As the name suggests, set of commands/scripts can be executed before git commit

Few days ago, I heard about this on some podcast (maybe changelog ? 🤷‍♂)

I have been using similar notation for my commits - even for this blog¹ - but I did not know it is a specification.

The idea is that very first word of the commit message should indicate what sort of commit is it.

Most common ones are : fix, feat (To indicate bugfix and a feature)

Other useful ones are: docs, style, refactor, test

Then there is chore (catch all ? 😄)

I’ve used some of these at work as well.

As the website mentions, benefit of such style is that some tools can parse the git log to automatically generate the changelog.

Website also mentions, that

it’s not the end of the world if a commit lands that does not meet the Conventional Commits specification. It simply means that commit will be missed by tools that are based on the spec.