--

Knowing that they changed a given line in a given PR (bugfix or feature) didn't help me a single time when I was at the company requiring squash commits.

Best practice is to make atomic commits and write informative commit messages with 10+ words. That makes it much easier to figure out why any given line changed.

Try it before you hate on 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.

No responses yet