--

Like other commentators have pointed out, commit messages are part of the codebase, and I don't like to get rid of them.

I never saw a single advantage of squash commits when using them universally -- rollbacks weren't any easier or harder in that environment.

But just yesterday I was able to fix a bug introduced by another developer much quicker because I had detailed commit history and could compare the individual commit that introduced the regression to the PR that included that commit and to the release that released it.

--

--

Dr. Derek Austin 🥳
Dr. Derek Austin 🥳

Written by Dr. Derek Austin 🥳

Hi, I'm Doctor Derek! I've been a professional web developer since 2005, and I love writing about programming with JavaScript, TypeScript, React, Next.js & Git.

Responses (1)