Daily Software Tips & Tricks

Ever look back at your git history and see ten commits in a row titled "fix", "typo", or "trying again"? It makes it a nightmare for anyone trying to review your work or track down where a bug was introduced. Before you merge that feature branch, try using a rebase to squash those tiny, incremental changes into one cohesive, meaningful commit. It keeps the main branch readable and makes you look like a pro who knows exactly what they are doing.

Using git rebase -i HEAD~[number of commits] allows you to pick which commits to keep and which to meld into the previous ones. It is a small extra step that makes a massive difference for the maintainability of your project's history.