How to squash commits

Make sure your branch is up to date with the master branch. Run git rebase -i master . You should see a list of commits, each commit starting with the word pick. Make sure the first commit says pick and change the rest from pick to squash. Save and close the editor.

Likewise, can I squash pushed commits? Git will then give you the opportunity to change your commit message to something like, Issue #100: Fixed retweet bug. Important: If youve already pushed commits to GitHub, and then squash them locally, you will have to force the push to your branch.

Also to know, why do squash commit?

Commit squashing has the benefit of keeping your git history tidy and easier to digest than the alternative created by merge commits. While merge commits retain commits like “oops missed a spot” and “maybe fix that test? [round 2]”, squashing retains the changes but omits the individual commits from history.

Is squashing commits a good idea?

Squash = Yes. For a simple project with no sharing between devs required and regular releases, then squashing features seems like a good idea if you: Keep detailed commit messages when you squash.