#GIT SQUASH COMMITS HOW TO#

Use the -i flag with the Git Rebase command to use the interactive mode. We can squash commits by using the interactive Git Rebase. The interactive mode gives us a lot of options to work with. The Git Rebase command works in two modes - Standard and Interactive.

#GIT SQUASH COMMITS HOW TO#

Let's learn how to use each of these commands. We can also use the Git Merge command with the squash option to combine commits before merging. The interactive mode of the Git Rebase command is mostly used to squash commits. Squashing is a matter of preference and how our team wants to maintain the Git workflow.This way we have all the changes merged with the master and we have a cleaner commit history. Instead, if we squash all the commits of the branch before merging it, then we will just end up with a single commit and that commit will be added to the history of our master branch.This will make it difficult to understand what actually is happening in our repository. We may work on several different branches which can have multiple commits and, merging these branches into the master branch will add a lot of commits to the history of our master branch.Squashing is usually done to keep our commit history clean and easy to understand.Let's try to understand why we need to squash commits. It is usually done before merging branches. Squashing commits is something that we will often do when collaborating with other developers to make our work more presentable and easy to understand. All the changes of the commits are added to a single commit point. In this tutorial, we will learn more about the need to squash and how we can squash commits.Īs discussed above, squashing is the process of combining multiple commits into a single one. We can use the interactive Git Rebase command to squash commits. Git does not provide us with a dedicated command to squash commits. In Git terminology, squash means to merge or combine multiple commits into a single one.

Git squash commits