Git squash commits in the middle of a branch

I want to squash several commits together in the middle of a branch without modifying the commits before and after.

I have :

  • To use <git push> on Visual Studio Code, but show “Could not read from remote repository.”
  • git rebase merge conflict
  • how do I determine whether git history is linear?
  • How do I exit from the text window in Git?
  • 'git submodule update --init --recursive' VS 'git submodule foreach --recursive git submodule update --init'
  • How to Git Ignore These Files
  • A -- B -- C -- D -- E -- F -- G
    |                             |
    master                        dev
    origin/master
    

    I want to squash that into

    A -- H -- E -- F -- G
    |                   |
    master              dev
    origin/master
    

    Where H is equivalent to B -- C -- D. And I want to be able to specify the commit message of H. A is the last commit that has been pushed so all commits after that can be rewritten without messing up the server. The idea is to clean up the history before I fast forward master.

    How can I do that ?

    PS: Note that in my case I actually have a lot more than 3 commits to squash in the middle, but if I can do it with 3, I should be able to do it with more.

    PPS: Also, if possible, I would prefer a solution where E, F and G remain untouched (mostly regarding the commit date).

  • Executing git commands on a bare repository
  • Running System32 programs instead of SysWOW64 when launching from MINGW
  • Continuing partial git svn dcommit after failed pre-commit hook
  • How to git pull rebase using GitPython library?
  • git: pull specific branch, keep only the latest tree (without any history)
  • Git clone through a reverse tunnel
  • One Solution collect form web for “Git squash commits in the middle of a branch”

    You can do an interactive rebase and hand select the commits which you want to squash. This will rewrite the history of your dev branch, but since you have not pushed these commits, there should not be any negative aftermath from this besides what might happen on your own computer.

    Start with the following:

    git checkout dev
    git rebase -i HEAD~6
    

    This should bring up a window showing you the following list of 7 commits, going back 6 steps from the HEAD of your dev branch:

    pick 07c5abd message for commit A
    pick dl398cn message for commit B
    pick 93nmcdu message for commit C
    pick lst28e4 message for commit D
    pick 398nmol message for commit E
    pick 9kml38d message for commit F
    pick 02jmdmp message for commit G
    

    The first commit shown (A above) is the oldest and the last is the most recent. You can see that by default, the option for each commit is pick. If you finished the rebase now, you would just be retaining each commit as it is, which is effectively a no-op. But since you want to squash certain middle commits, edit and change the list to this:

    pick 07c5abd message for commit A
    pick dl398cn new commit message for "H" goes here
    squash 93nmcdu message for commit C
    squash lst28e4 message for commit D
    pick 398nmol message for commit E
    pick 9kml38d message for commit F
    pick 02jmdmp message for commit G
    

    Note carefully what is happening above. By typing squash you are telling Git to merge that commit into the one above it, which is the commit which came immediately before it. So this says to squash commit D backwards into commit C, and then to squash C into B, leaving you with just one commit for commits B, C, and D. The other commits remain as is.

    Save the file (: wq on Git Bash in Windows), and the rebase is complete. Keep in mind you can get merge conflicts from this as you might expect, but there is nothing special about resolving them and you can carry on as you would with any regular rebase or merge.

    If you inspect the branch after the rebase, you will notice that the E, F, and G commits now have new hashes, dates, etc. This is because these commits have actually been replaced by new commits. The reason for this is that you rewrote history, and therefore the commits in general can no longer be the same as they were previously.

    Git Baby is a git and github fan, let's start git clone.