Working on legacy code bases and I've decided commits messages similar to "fixed typo" can ruin a commit history which will often contain important contextual information. Include a typo fix in a non related commit message can also ruin the commit history. Using commit --fixup and rebase --autosquash developers can update existing commits.

Often developers who are unfamiliar with git are too shy to even think about updating their git history. Here are three simple steps you can do to improve your history and make your repository easier to understand.