943

My issue is I have changed a file e.g.: README, added a new line 'this for my testing line' and saved the file, then I issued the following commands:

git status # On branch master # Changed but not updated: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: README # no changes added to commit (use "git add" and/or "git commit -a") git add README git commit -a -m 'To add new line to readme'

I didn't push the code to GitHub. Now I want to cancel this commit.

For this, I used

git reset --hard HEAD~1

But I lost the newly added line 'this for my testing line' from the README file. This should not happen. I need the content to be there. Is there a way to retain the content and cancel my local commit?

Improve this question
2
  • 3
    It sounds like you're definitely not asking for git revert, which creates a new commit with the reverse diff of the reverted commit. Resetting simply points your current branch to a different commit, in this case, the one before the commit you want to "forget". Commented Jan 31, 2011 at 16:11
  • 2
    NB: Might be worth mentioning that git-commit can abort if you leave the message blank, so if you haven't actually finished the commit that could be helpful. Commented Feb 24, 2014 at 17:08

8 Answers 8

Reset to default
1736

Just use git reset without the --hard flag:

git reset HEAD~1

PS: On Unix based systems you can use HEAD^ which is equal to HEAD~1. On Windows HEAD^ will not work because ^ signals a line continuation. So your command prompt will just ask you More?.

Improve this answer
Sign up to request clarification or add additional context in comments.

7 Comments

By the way, this is called --mixed in the manual.
Newer versions of Git even allow @^ as a shorthand for HEAD^.
I don't know what this did, but a lot of files appeard on my change list, files I didn't touch
@feresr If you really did not touch those files in the last commit or in the working tree this is caused by other inconsistencies in your working tree, e.g. you're on Windows and file endings do not match.
is it possible to reset all commit on one hand?
|
295

Use --soft instead of --hard flag.

Unix:

git reset --soft HEAD^

Windows:

git reset --soft HEAD~

It will remove the last local (unpushed) commit, but will keep changes you have done.

Improve this answer

3 Comments

If you open Package Manager Console and run this "git reset --soft HEAD^", it does what you want (and what I needed).
@fider Saviour! Not sure if the accepted answer still works, but this should be the exact answer the OP needed.
git reset --soft HEAD~ on windows
68

If you're in the middle of a commit (i.e. in your editor already), you can cancel it by deleting all lines above the first #. That will abort the commit.

So you can delete all lines so that the commit message is empty, then save the file:

It should look like this.

You'll then get a message that says Aborting commit due to empty commit message..

Improve this answer

2 Comments

This is exactly what I was looking for! This answer needs more upvotes :)
FYI, this also works if you are trying to abort a rebase -i mybranchname
38

The first thing you should do is to determine whether you want to keep the local changes before you delete the commit message.

Use git log to show current commit messages, then find the commit_id before the commit that you want to delete, not the commit you want to delete.

If you want to keep the locally changed files, and just delete commit message:

git reset --soft commit_id

If you want to delete all locally changed files and the commit message:

git reset --hard commit_id

That's the difference of soft and hard

Improve this answer

1 Comment

I think it's the opposite.
12

You can tell Git what to do with your index (set of files that will become the next commit) and working directory when performing git reset by using one of the parameters:

--soft: Only commits will be reseted, while Index and the working directory are not altered.

--mixed: This will reset the index to match the HEAD, while working directory will not be touched. All the changes will stay in the working directory and appear as modified.

--hard: It resets everything (commits, index, working directory) to match the HEAD.

In your case, I would use git reset --soft to keep your modified changes in Index and working directory. Be sure to check this out for a more detailed explanation.

Improve this answer

Comments

9

Use below command:

$ git reset HEAD~1

After this you also able to view files what revert back like below response.

Unstaged changes after reset: M application/config/config.php M application/config/database.php
Improve this answer

Comments

4

As @Amal Kumar say. Just use git commmand:

git reset HEAD~1
Improve this answer

1 Comment

This will delete your local master branch and all your changes will be lost. It's better not to delete the branch. You can use git reset HEAD~1 this will cancel your last git commit that was not pushed to remote and the changes won't be lost. You can also go through the different answers posted here for different use cases.
1

Here I ran into another situation.

I have 2 branchs, one is 'dev', one is 'new', I fixed one bug on dev, then on new:

git rebase origin/dev git push -f

The new branch now is running on server, while I update new on server, git add some local commits for me:

git pull # On branch new # Your branch and 'origin/new' have diverged, # and have 7 and 10 different commits each, respectively. # (use "git pull" to merge the remote branch into yours) # nothing to commit, working tree clean

'git pull' not work...

'git reset HEAD~1' not work...

I use

git reset origin/new

to get work done.

Improve this answer

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.