No, there's no reason to preserve commit messages you used during development. When I am developing, I make many tiny commits with an automatically generated t

No, there's no reason to preserve commit messages you used during development. When I am developing, I make many tiny commits with an automatically generated title ('Modify util/files.py') each time my tests pass, or really, when I do anything of value. (I use `git-infer`: https://github.com/rec/gitz/blob/master/git-infer https://github.com/rec/gitz/blob/master/git-infer) This makes it impossible for me to lose work, and acts like a coarse-grained undo for me, where I can quickly move back and forth between spots that the tests worked if I decide I'm going the wrong way, or create a new branch, move back a bit, and make some changes and compare. _Before anyone sees this code_ I rebase it down to a logical sequence extremely-carefully named and organized commits. (The word "manicured" has been used more than once.) As I go through code review, I make tiny commits and at the end, rebase them into my carefully-named commits. I create at least five commit IDs for each final commit I created. No one wants to see these. I spend considerable time organizing everything so just the information you need to see is in the final commits. All the information should be there.