Skip to content

Instantly share code, notes, and snippets.

@n00neimp0rtant
Last active June 8, 2026 10:47
Show Gist options
  • Select an option

  • Save n00neimp0rtant/9515611 to your computer and use it in GitHub Desktop.

Select an option

Save n00neimp0rtant/9515611 to your computer and use it in GitHub Desktop.
simple squash without rebase
## within current branch, squashes all commits that are ahead of master down into one
## useful if you merged with upstream in the middle of your commits (rebase could get very ugly if this is the case)
## commit any working changes on branch "mybranchname", then...
git checkout master
git checkout -b mybranchname_temp
git merge --squash mybranchname
git commit -am "Message describing all squashed commits"
git branch -m mybranchname mybranchname_unsquashed
git branch -m mybranchname
## optional, not recommended if you want to keep the unsquashed history around for a bit longer
git branch -D mybranchname_unsquashed
## if squashing already-pushed commits...
git push --force
@mollyretter

Copy link
Copy Markdown

thank you for saving me from rebase hell 👍 ➕

@Qiki

Qiki commented Aug 5, 2016

Copy link
Copy Markdown

I used for three years. Scott! you are the best!

@damianmr

Copy link
Copy Markdown

Thank you, this is a masterpiece of gitmanship :squirrel:

@DevSide

DevSide commented Dec 7, 2016

Copy link
Copy Markdown

Another way, you can rebase on the parent of your first commit which is the pointer where your branch diverged.

git rebase -i FIRST_COMMIT_SHA1~

@aseem2625

Copy link
Copy Markdown

lol.. I actually had to get some conflicts with rebase with master.. But above steps effectively got me the same thing as below could do:

  1. git reset --soft HEAD^^^ (as many new commits in your feature branch. Now, you can see all your changed files in git st )
  2. git stash (stashing all changed files of feature branch)
  3. git rebase master (no conflicts because feature branch now has no commits of its own)
  4. git stash pop (with conflicts in your changed files adding <<<< ==== wherever you made changes in your files..)

Anyways, this is good enough.

@shahi645

shahi645 commented Aug 25, 2017

Copy link
Copy Markdown

cheers bro, swish swish swish...another one bites the dust

@ncullen

ncullen commented Apr 17, 2018

Copy link
Copy Markdown

I frequently consult this GIST as I can never remember how to do this, and wish it were a single command in git. Thank you so much for saving me from rebase hell.

@shahi645

Copy link
Copy Markdown

Cheers again bro!

@sgupta-paymerang

Copy link
Copy Markdown

Thanks a lot !! You saved my time :)

@shahi645

Copy link
Copy Markdown

Once again this has served me well...thanks!

@shahi645

Copy link
Copy Markdown

Fair play, this has once again pulled me from the darkness

@shahi645

shahi645 commented Oct 8, 2018

Copy link
Copy Markdown

Nice one m8!

@dbcoderain

Copy link
Copy Markdown

Brilliant, thanks for this

@chengwhynot

Copy link
Copy Markdown

cool

@HelloBanksy

Copy link
Copy Markdown

Note that you might face the issue of setting tracking information as well (connecting your new squashed branch to your remote one). To handle this you will need to do:
git branch --set-upstream-to=origin/myfeaturebranch myfeaturebranch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment