How do I delete unpushed git commits

Question

I accidentally committed to the wrong branch  How do I delete that commit

User · Answer

Do a git rebase -i FAR ENOUGH BACK and drop the line for the commit you don t want

User · Answer

Following command worked for me  all the local committed changes are dropped  amp  local is reset to the same as remote origin master branch      git reset --hard origin

User · Answer

For your reference  I believe you can  hard cut  commits out of your current branch not only with git reset --hard  but also with the following command   git checkout -B  lt branch-name gt   lt SHA gt    In fact  if you don t care about checking out  you can set the branch to whatever you want with   git branch -f  lt branch-name gt   lt SHA gt    This would be a programmatic way to remove commits from a branch  for instance  in order to copy new commits to it  using rebase    Suppose you have a branch that is disconnected from master because you have taken sources from some other location and dumped it into the branch   You now have a branch in which you have applied changes  let s call it  topic    You will now create a duplicate of your topic branch and then rebase it onto the source code dump that is sitting in branch  dump    git branch topic duplicate topic git rebase --onto dump master topic duplicate   Now your changes are reapplied in branch topic duplicate based on the starting point of  dump  but only the commits that have happened since  master   So your changes since master are now reapplied on top of  dump  but the result ends up in  topic duplicate    You could then replace  dump  with  topic duplicate  by doing   git branch -f dump topic duplicate git branch -D topic duplicate   Or with  git branch -M topic duplicate dump   Or just by discarding the dump  git branch -D dump   Perhaps you could also just cherry-pick after clearing the current  topic duplicate    What I am trying to say is that if you want to update the current  duplicate  branch based off of a different ancestor you must first delete the previously  cherrypicked  commits by doing a git reset --hard  lt last-commit-to-retain gt  or git branch -f topic duplicate  lt last-commit-to-retain gt  and then copying the other commits over  from the main topic branch  by either rebasing or cherry-picking   Rebasing only works on a branch that already has the commits  so you need to duplicate your topic branch each time you want to do that   Cherrypicking is much easier   git cherry-pick master  topic   So the entire sequence will come down to   git reset --hard  lt latest-commit-to-keep gt  git cherry-pick master  topic   When your topic-duplicate branch has been checked out  That would remove previously-cherry-picked commits from the current duplicate  and just re-apply all of the changes happening in  topic  on top of your current  dump   different ancestor   It seems a reasonably convenient way to base your development on the  real  upstream master while using a different  downstream  master to check whether your local changes also still apply to that  Alternatively you could just generate a diff and then apply it outside of any Git source tree  But in this way you can keep an up-to-date modified  patched  version that is based on your distribution s version while your actual development is against the real upstream master   So just to demonstrate    reset will make your branch point to a different commit  --hard also checks out the previous commit  --soft keeps added files in the index  that would be committed if you commit again  and the default  --mixed  will not check out the previous commit  wiping your local changes  but it will clear the index  nothing has been added for commit yet  you can just force a branch to point to a different commit you can do so while immediately checking out that commit as well rebasing works on commits present in your current branch cherry-picking means to copy over from a different branch   Hope this helps someone  I was meaning to rewrite this  but I cannot manage now  Regards

User · Answer

If you want to move that commit to another branch  get the SHA of the commit in question  git rev-parse HEAD   Then switch the current branch  git checkout other-branch   And cherry-pick the commit to other-branch  git cherry-pick  lt sha-of-the-commit gt

User · Answer

Delete the most recent commit  keeping the work you ve done   git reset --soft HEAD 1   Delete the most recent commit  destroying the work you ve done   git reset --hard HEAD 1

User · Answer

Don t delete it  for just one commit git cherry-pick is enough   But if you had several commits on the wrong branch  that is where git rebase --onto shines   Suppose you have this    x--x--x--x  lt -- master                          -y--y--m--m  lt - y branch  with commits which should have been on master     then you can mark master and move it where you would want to be    git checkout master  git branch tmp  git checkout y  git branch -f master   x--x--x--x  lt -- tmp                          -y--y--m--m  lt - y branch  master branch     reset y branch where it should have been    git checkout y  git reset --hard HEAD 2    1 in your case                              or  n  n   number of commits to cancel   x--x--x--x  lt -- tmp                          -y--y--m--m  lt - master branch                                                     -- y branch     and finally move your commits  reapply them  making actually new commits    git rebase --onto tmp y master  git branch -D tmp    x--x--x--x--m --m   lt -- master                          -y--y  lt - y branch

User · Answer

I wonder why the best answer that I ve found is only in the comments   by Daenyth with 86 up votes   git reset --hard origin   This command will sync the local repository with the remote repository getting rid of every change you have made on your local   You can also do the following to fetch the exact branch that you have in the origin   git reset --hard origin  lt branch gt

[git] How do I delete unpushed git commits?

Examples related to git