Optimize the commit history for review and archaeology. Use the possibility to rewrite history before branch is integrated.
History is written by the victors
When developing all details of how something should be implemented is often not known until it is done. This usually leads to a messy commit log for the feature branch. Before integrating it, take a step back, now that the end result is known, how can that be reached in a step-wise way with commits that are easy to understand.
Hiding detours and mistakes done while developing will make commit history (and you!) look good. This makes reviewers and future readers job easier.
"The commit message history provides the Director's commentary"
"Noone knows how long it took, everyone can see the end result."