My Git history looks like that :
I would like to squash the purple commits into a single one. I don't want to see them ever again in my commit log.
I've tried to do a git rebase -i 1
, but even though 1
is on the blue branch (cf. picture), I still see every commit on my purple branch.
How can I completely remove the purple branch (from commit log) ?
This question is related to
git
git-merge
git-rebase
Starting with the repo in the original state
To remove the merge commit and squash the branch into a single commit in the mainline
Use these commands (replacing 5 and 1 with the SHAs of the corresponding commits):
git checkout 5
git reset --soft 1
git commit --amend -m '1 2 3 4 5'
git rebase HEAD master
To retain a merge commit but squash the branch commits into one:
Use these commands (replacing 5, 1 and C with the SHAs of the corresponding commits):
git checkout -b tempbranch 5
git reset --soft 1
git commit --amend -m '1 2 3 4 5'
git checkout C
git merge --no-ff tempbranch
git rebase HEAD master
To remove the merge commit and replace it with individual commits from the branch
Just do (replacing 5 with the SHA of the corresponding commit):
git rebase 5 master
And finally, to remove the branch entirely
Use this command (replacing C and D with the SHAs of the corresponding commits):
git rebase --onto C D~ master
There are two ways to tackle this based on what you want:
Solution 1: Remove purple commits, preserving history (incase you want to roll back)
git revert -m 1 <SHA of merge>
-m 1
specifies which parent line to choose
Purple commits will still be there in history but since you have reverted, you will not see code from those commits.
Solution 2: Completely remove purple commits (disruptive change if repo is shared)
git rebase -i <SHA before branching out>
and delete (remove lines) corresponding to purple commits.
This would be less tricky if commits were not made after merge. Additional commits increase the chance of conflicts during revert/rebase
.
If all you want to do is to remove a merge commit (2) so that it is like it never happened, the command is simply as follows
git rebase --onto <sha of 1> <sha of 2> <blue branch>
And now the purple branch isn't in the commit log of blue at all and you have two separate branches again. You can then squash the purple independently and do whatever other manipulations you want without the merge commit in the way.
Source: Stackoverflow.com