Menu
In order to revert changes in a working tree and index, this answer (https://stackoverflow.com/a/5812972/8278160) suggests that one run the following:
git reset --hard
Would running this be the same as running git reset --hard HEAD?
297
Other than that, it will not bring about any changes to your index, nor will it change your current working directory. So, in short, we can say that “git reset” is a command, whereas “git reset –hard” is its variation that is used when you want to wipe out all the traces of your last commit.
The git reset HEAD~2 command moves the current branch backward by two commits, effectively removing the two snapshots we just created from the project history. Remember that this kind of reset should only be used on unpublished commits.
git reset --soft , which will keep your files, and stage all changes back automatically. git reset --hard , which will completely destroy any changes and remove them from the local directory.
"pull" has not made merge commit, so git reset --hard which is a synonym for git reset --hard HEAD clears the mess from the index file and the working tree. Merge a topic branch into the current branch, which resulted in a fast-forward.
Yes, HEAD is implied if not specified, so it's the same thing.
Source [bullet item #2]
164
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
