Delete commits from a branch in Git

Question

I would like to know how to delete a commit   By delete  I mean it is as if I didn t make that commit  and when I do a push in the future  my changes will not push to the remote branch   I read git help  and I think the command I should use is git reset --hard HEAD   Is this correct

User · Answer

git reset --hard HEAD 1 You will be now at previous head  Pull the branch  Push new code  Commit will be removed from git

User · Answer

Source  https   gist github com sagarjethi c07723b2f4fa74ad8bdf229166cf79d8  Delete the last commit  For example  your last  commit   git push origin  aa61ab32  master  Now you want to delete this commit then an Easy way to do this following  Steps    First reset the branch to the parent of the current commit  Force-push it to the remote     git reset HEAD  --hard  git push origin -f    For particular commit  you want to reset is following  git reset bb676878  --hard  git push origin -f

User · Answer

To delete in local branch  use  git reset --hard HEAD 1   To delete in a remote branch  use   git push origin HEAD --force

User · Answer

If you have not yet pushed the commit anywhere  you can use git rebase -i to remove that commit  First  find out how far back that commit is  approximately   Then do   git rebase -i HEAD N   The  N means rebase the last N commits  N must be a number  for example HEAD 10   Then  you can edit the file that Git presents to you to delete the offending commit  On saving that file  Git will then rewrite all the following commits as if the one you deleted didn t exist   The Git Book has a good section on rebasing with pictures and examples   Be careful with this though  because if you change something that you have pushed elsewhere  another approach will be needed unless you are planning to do a force push

User · Answer

If you want to fix up your latest commit  you can undo the commit  and unstage the files in it  by doing   git reset HEAD 1   This will return your repository to its state before the git add commands that staged the files  Your changes will be in your working directory  HEAD 1 refers to the commit below the current tip of the branch   If you want to uncommit N commits  but keep the code changes in your working directory   git reset HEAD N   If you want to get rid of your latest commit  and do not want to keep the code changes  you can do a  hard  reset   git reset --hard HEAD 1   Likewise  if you want to discard the last N commits  and do not want to keep the code changes   git reset --hard HEAD N

User · Answer

Here s another way to do this   Checkout the branch you want to revert  then reset your local working copy back to the commit that you want to be the latest one on the remote server  everything after it will go bye-bye   To do this  in SourceTree I right-clicked on the and selected  Reset BRANCHNAME to this commit   I think the command line is   git reset --hard COMMIT ID   Since you just checked out your branch from remote  you re not going to have any local changes to worry about losing  But this would lose them if you did   Then navigate to your repository s local directory and run this command   git -c diff mnemonicprefix false -c core quotepath false   push -v -f --tags REPOSITORY NAME BRANCHNAME BRANCHNAME   This will erase all commits after the current one in your local repository but only for that one branch

User · Answer

Assuming you have not pushed to the remote repository  you could re-clone the repository  This has been my method of choice a few times

User · Answer

git reset --hard   git push origin HEAD --force  If one or more of the commits is tagged  delete the tag s  first  Otherwise the tagged commit is not removed

User · Answer

git reset --hard commitId  git push  lt origin gt   lt branch gt  --force   PS  CommitId refers the one which you want to revert back to

User · Answer

If you ve already pushed  first find the commit you want to be at HEAD   GIT COMMIT HASH HERE   then run the following   git reset --hard  GIT COMMIT HASH HERE git push origin HEAD --force   Then each place the repo has been cloned  run   git reset --hard origin master

User · Answer

If you didn t publish changes  to remove latest commit  you can do    git reset --hard HEAD     note that this would also remove all uncommitted changes  use with care    If you already published to-be-deleted commit  use git revert    git revert HEAD

User · Answer

Quick Answer   You have many alternatives  for example    Alternative 1   git rebase -i  lt YourCommitId gt  1      Change YourCommitId for the number of the commit which you want to revert back to   Alternative 2   git reset --hard YourCommitId git push  lt origin gt   lt branch gt  --force      Change YourCommitId for the number of the commit which you want to revert back to       I don t recommend this option because you can lost your work in progress   Alternative 3   git reset --soft HEAD 1      You can keep your work and only undo the commit

User · Answer

Removing an entire commit  git rebase -p --onto SHA  SHA   Obviously replace  SHA  with the reference you want to get rid of  The     in that command is literal   http   sethrobertson github io GitFixUm fixup html change deep

User · Answer

In my case  my magic code for this pupose is this one   git reset --hard   u    Test it and tell me  I have tried a few different ones  but this one was the only that helped me

User · Answer

Say we want to remove commits 2  amp  4 from the repo    commit 0   b3d92c5 commit 1   2c6a45b commit 2    lt any hash gt  commit 3   77b9b82 commit 4    lt any hash gt    Note  You need to have admin rights over the repo since you are using --hard and -f    git checkout b3d92c5 Checkout the last usable commit  git checkout -b repair Create a new branch to work on  git cherry-pick 77b9b82 Run through commit 3  git cherry-pick 2c6a45b Run through commit 1  git checkout master Checkout master  git reset --hard b3d92c5 Reset master to last usable commit  git merge repair Merge our new branch onto master  git push -f origin master Push master to the remote repo

User · Answer

display git commit log       git log --pretty oneline --abbrev-commit     show last two commit and open in your default editor    then delete second commit line and save it   git rebase -i HEAD 2   Reference  How to delete a commit in git  local and remote

User · Answer

Here I just post one clear pipeline to do so Step1  Use git log to get the commit ID  git log   Step2  Use git reset to go back to the former version  git reset --hard  lt your commit id gt

User · Answer

Take backup of your code in to temp folder  Following command will reset same as server   git reset --hard HEAD git clean -f git pull   If you want to keep your changes   and remove recent commits  git reset --soft HEAD  git pull

User · Answer

If you just messed up your last commit  wrong message  forgot to add some changes  and want to fix it before pushing it to a public repo why not use   git commit --amend -m  New message here    If you have newly staged changes they ll be combined with the last commit  that you re trying to get rid of  and will replace that commit   Of course if you amend a commit after you ve pushed it  you re rewriting history so if you do that be sure to understand the implications   You can also pass the  --no-edit  option instead of  -m  if you would prefer to use the previous commit s message   Docs  http   git-scm com docs git-commit html

User · Answer

As you can see on above image i want to delete revert test change 2  commit SHA1 ID  015b5220c50e3dfbb1063f23789d92ae1d3481a2 you can get SHA1 ID by using gitk command in git bash     For that i can use all below command work on local only  you need to push after delete     git reset --hard 515b5220c50e3dfbb1063f23789d92ae1d3481a2   it back-up you to that commit  SHA1 ID of test change 4 commit is 515b5220c50e3dfbb1063f23789d92ae1d3481a2   git reset --hard HEAD 1    it back-up you before one commit  git reset --hard HEAD      To remove the last commit from git   after delete

User · Answer

use git revert  https   git-scm com docs git-revert  It will revert all code then you can do next commit Then head will point to that last commit  reverted commits never delete but it will not affect on you last commit

User · Answer

All the commands above restore the state of your work tree and index as they were before making the commit  but do not restore the state of the repository  If you look at it  the  removed  commit is not actually removed  it is simply not the one on the tip of the current branch   I think that there are no means to remove a commit with porcelain commands  The only way is to remove it from the log and reflog and then to execute a git prune --expire -now

User · Answer

I m appending this answer because I don t see why anyone who has just tried to commit work would want to delete all that work because of some mistake using Git   If you want to keep your work and just  undo  that commit command  you caught before pushing to repo    git reset --soft HEAD 1   Do not use the --hard flag unless you want to destroy your work in progress since the last commit

User · Answer

I have already pushed  Need to return some commits back remotly  Have tried many variations   but only this from Justin via git bush is working fine for me   git reset --hard  GIT COMMIT HASH HERE git push origin HEAD --force

User · Answer

Careful  git reset --hard WILL DELETE YOUR WORKING DIRECTORY CHANGES  Be sure to stash any local changes you want to keep before running this command   Assuming you are sitting on that commit  then this command will wack it     git reset --hard HEAD 1   The HEAD 1 means the commit before head   Or  you could look at the output of git log  find the commit id of the commit you want to back up to  and then do this   git reset --hard  lt sha1-commit-id gt      If you already pushed it  you will need to do a force push to get rid of it     git push origin HEAD --force   However  if others may have pulled it  then you would be better off starting a new branch   Because when they pull  it will just merge it into their work  and you will get it pushed back up again   If you already pushed  it may be better to use git revert  to create a  mirror image  commit that will undo the changes   However  both commits will be in the log     FYI -- git reset --hard HEAD is great if you want to get rid of WORK IN PROGRESS   It will reset you back to the most recent commit  and erase all the changes in your working tree and index     Lastly  if you need to find a commit that you  deleted   it is typically present in git reflog unless you have garbage collected your repository

User · Answer

Reset on local branch   git reset --hard HEAD  lt Number of commit gt  So git reset --hard HEAD 3   Force push to origin  git push -f origin

User · Answer

The mistake   I git rebase -i --root ed my branch  ignorantly thinking I could reword the first commit differing from the master  the GitHub for Windows default view is the comparison to master  hiding it s entirety    I grew a Silicon Valley beard while 900  commits loaded themselves into Sublime  Exiting with no changes  I charged my battery then proceeded to shave  as all 900  individual commits nonchalantly rebased - resetting their commit times to now   Determined to beat Git and preserve the original times  I deleted this local repository and re-cloned from the remote   Now it had re-added a most recent unneeded commit to master I wished to remove  so proceeded like so   Exhausting the options   I didn t wish to git revert - it would create an additional commit  giving Git the upper hand   git reset --hard HEAD did nothing  after checking the reflog  the last and only HEAD was the clone - Git wins   To get the most recent SHA  I checked the remote repository on github com - minor win   After thinking git reset --hard  lt SHA gt  had worked  I updated another branch to master and 1    2    poof  the commit was back - Git wins   Checking back out to master  time to try git rebase -i  lt SHA gt   then remove the line    to no avail  sad to say   If you remove a line here THAT COMMIT WILL BE LOST   Ah   glossed over new feature troll the n00b in the 2 8 3 release notes   The solution   git rebase -i  lt SHA gt  then d  drop   remove commit   To verify  I checked out to another branch  and voila - no hiding commit to fetch pull from the master   https   twitter com holman status 706006896273063936  Good day to you

User · Answer

Another possibility is one of my personal favorite commands   git rebase -i  lt commit gt  1   This will start the rebase in interactive mode -i at the point just before the commit you want to whack  The editor will start up listing all of the commits since then  Delete the line containing the commit you want to obliterate and save the file  Rebase will do the rest of the work  deleting only that commit  and replaying all of the others back into the log

User · Answer

For me rebase did the trick   git rebase -i HEAD 98    Delete everything except for the most recent commit on the shown editor caused by  quot rebase quot     git push origin -f production-static  NOTE  After forcing the push to reduce my comments  I then pushed another set of files and then I tried pulled with the same  quot repository  amp  branch quot  on another computer  Surprisingly there is no conflict  This became my way to reduce repository size while avoiding pull conflicts on my other locals that uses the same git

User · Answer

git rebase -i HEAD 2   Here  2  is the number of commits you want to rebase       git rebase -i HEAD    if you want to rebase all the commits   Then you will be able to choose one of these options   p  pick   use commit  r  reword   use commit  but edit the commit message  e  edit   use commit  but stop for amending  s  squash   use commit  but meld into previous commit  f  fixup   like  squash   but discard this commit s log message  x  exec   run command  the rest of the line  using shell  d  drop   remove commit  These lines can be re-ordered  they are executed from top to bottom   If you remove a line here THAT COMMIT WILL BE LOST   However  if you remove everything  the rebase will be aborted   Note that empty commits are commented out  You can simply remove that commit using option  d  or Removing a line that has your commit

User · Answer

What I do usually when I commit and push  if anyone pushed his commit this solve the problem    git reset --hard HEAD 1  git push -f origin   hope this help

User · Answer

Forcefully Change History  Assuming you don t just want to delete the last commit  but you want to delete specific commits of the last n commits  go with   git rebase -i HEAD  lt number of commits to go back gt   so git rebase -i HEAD 5 if you want to see the last five commits   Then in the text editor change the word pick to drop next to every commit you would like to remove  Save and quit the editor  Voila   Additively Change History  Try git revert  lt commit hash gt   Revert will create a new commit that undoes the specified commit

User · Answer

If you want to keep the history  showing the commit and the revert  you should use   git revert GIT COMMIT HASH   enter the message explaining why are you reverting and then   git push     When you issue git log you ll see both the  wrong  commit and revert log messages

[git] Delete commits from a branch in Git

Examples related to git

Examples related to git-rebase

Examples related to git-reset