{"id":1841,"date":"2017-12-06T08:50:09","date_gmt":"2017-12-06T08:50:09","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/?p=1841"},"modified":"2025-02-01T22:47:38","modified_gmt":"2025-02-01T22:47:38","slug":"git-reset-vs-git-revert","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/git-reset-vs-git-revert\/","title":{"rendered":"Git Commands Tutorials and Example: Git Reset – Git Revert"},"content":{"rendered":"

 git reset Vs git revert<\/strong>
\ngit reset Vs git revert<\/p>\n

The git revert command undoes a committed snapshot. But, instead of removing the commit from the project history, it figures out how to undo the changes introduced by the commit and appends a new commit with the resulting content. This prevents Git from losing history, which is important for the integrity of your revision history and for reliable collaboration.<\/p>\n

git revert<\/p>\n

Reverting vs. Resetting
\nIt’s important to understand that git revert undoes a single commit\u2014it does not “revert” back to the previous state of a project by removing all subsequent commits. In Git, this is actually called a reset, not a revert.\\<\/p>\n

Reverting has two important advantages over resetting. First, it doesn\u2019t change the project history, which makes it a \u201csafe\u201d operation for commits that have already been published to a shared repository. For details about why altering shared history is dangerous, please see the git reset page.<\/p>\n

Second, git revert is able to target an individual commit at an arbitrary point in the history, whereas git reset can only work backwards from the current commit. For example, if you wanted to undo an old commit with git reset, you would have to remove all of the commits that occurred after the target commit, remove it, then re-commit all of the subsequent commits. Needless to say, this is not an elegant undo solution.<\/p>\n

git reset<\/p>\n

If git revert is a \u201csafe\u201d way to undo changes, you can think of git reset as the dangerous method. When you undo with git reset(and the commits are no longer referenced by any ref or the reflog), there is no way to retrieve the original copy\u2014it is a permanent undo. Care must be taken when using this tool, as it\u2019s one of the only Git commands that has the potential to lose your work.<\/p>\n

Usage<\/p>\n

git reset<\/p>\n

Remove the specified file from the staging area, but leave the working directory unchanged. This unstages a file without overwriting any changes.<\/p>\n

git reset<\/p>\n

Reset the staging area to match the most recent commit, but leave the working directory unchanged. This unstages all files without overwriting any changes, giving you the opportunity to re-build the staged snapshot from scratch.<\/p>\n

git reset –hard<\/p>\n

Reset the staging area and the working directory to match the most recent commit. In addition to unstaging changes, the –hard flag tells Git to overwrite all changes in the working directory, too. Put another way: this obliterates all uncommitted changes, so make sure you really want to throw away your local developments before using it.<\/p>\n

git reset<\/p>\n

Move the current branch tip backward to , reset the staging area to match, but leave the working directory alone. All changes made since will reside in the working directory, which lets you re-commit the project history using cleaner, more atomic snapshots.<\/p>\n

git reset –hard<\/p>\n

Move the current branch tip backward to and reset both the staging area and the working directory to match. This obliterates not only the uncommitted changes, but all commits after , as well.
\nRegards,
\nRajesh Kumar
\nTwitt me @ twitter.com\/RajeshKumarIn<\/a><\/p>\n

rajeshkumar replied the topic: git reset Vs git revert<\/strong>
\nMore Reference —<\/p>\n

www.atlassian.com\/git\/tutorial\/undoing-changes#!revert <\/a>
\nwww.atlassian.com\/git\/tutorial\/undoing-changes#!reset<\/a>
\nRegards,
\nRajesh Kumar
\nTwitt me @ twitter.com\/RajeshKumarIn<\/a><\/p>\n\n