Write good git commit messages
Writing good commit messages is one of those things that IMO make the difference between a dev who produces good code, and a dev who produces high quality work in general.<p>The git log is one of the main entry points to an open source (or closed source, in fact) project. Following them tells a story, and can help you understand decisions made.<p>Imagine you have two projects to bisect. One of them has clean, atomic and descriptive commits. The other has a git log that looks like this: <a href="https://github.com/pypa/pipenv/commits/master?after=d4d54eeb39ef45a9b68c78b8fc8f66c3f5396691+1154" rel="nofollow">https://github.com/pypa/pipenv/commits/master?after=d4d54eeb...</a><p>I know which one I'd want to debug. This is also the primary reason why I highly dislike merge commits: They make git logs extremely unreadable.<p>The thing is that writing clean commits is something that is extremely easy to do. Unlike docs and tests, it's not more work (it's less, in fact) and it's not something to continuously maintain as the code changes. It's an immediate improvement you can make to your development habits that will have a consequential improvement to your QOL. You <i>will</i> catch bugs doing this!<p>(Tip when writing atomic commits: Use `git add -p`. That lets you stage patch hunks.)