I think it depends a lot on your process as well. I should have added that we use Jira+Confluence and every merge commit starts with ENG-1234 | Does the ne

I think it depends a lot on your process as well. I should have added that we use Jira+Confluence and every merge commit starts with ENG-1234 | Does the needful with foobar So most of the context is in the tickets, which then point to design docs. The code has very high percentage of docstrings, very high type coverage (for Python anyways), so there's really not much to be had in commit messages. We are a small (<20) team of engineers in a fast-moving year-old startup. Very tight slack comms. PRs to main are often single-digit lines, typically a few dozen, and anything more than a few hundred LOC is considered suboptimal. I think if you are running an open-source project, with lots of disparate contributors, using Git as your main knowledge base, with bigger PRs, it's a very different ballgame. I think in that situation I would be team history.