How Do You Roll Back (Reset) a Git Repository to a Particular Commit? [Duplicate]
I Cloned a Git Repository and Then Tried to Roll It Back to a Particular Commit Early on in the Development Process. Everything That Was Added to the...
![How Do You Roll Back (Reset) a Git Repository to a Particular Commit? [Duplicate]](https://www.alledaags.nl/uploads/how-do-you-roll-back-reset-a_1200.jpg)
I cloned a Git repository and then tried to roll it back to a particular commit early on in the development process. Everything that was added to the repository after that point is unimportant to me so I want to omit all subsequent changes from my local source code.
However, when I try to roll back in the GUI tool it doesn't update my local file system - I always end up with the latest source code for the project.
What's the correct way to just get the source for a repository as of a particular commit in the project's history and omit all later updates?
4 Answers
git reset --hard <tag/branch/commit id>
Notes:
git resetwithout the--hardoption resets the commit history, but not the files. With the--hardoption the files in working tree are also reset. (credited user)If you wish to commit that state so that the remote repository also points to the rolled back commit do:
git push <reponame> -f(credited user)
Must Read
Update:
Because of changes to how tracking branches are created and pushed I no longer recommend renaming branches. This is what I recommend now:
Make a copy of the branch at its current state:
git branch crazyexperiment
(The git branch <name> command will leave you with your current branch still checked out.)
Reset your current branch to your desired commit with git reset:
git reset --hard c2e7af2b51
(Replace c2e7af2b51 with the commit that you want to go back to.)
When you decide that your crazy experiment branch doesn't contain anything useful, you can delete it with:
git branch -D crazyexperiment
It's always nice when you're starting out with history-modifying git commands (reset, rebase) to create backup branches before you run them. Eventually once you're comfortable you won't find it necessary. If you do modify your history in a way that you don't want and haven't created a backup branch, look into git reflog. Git keeps commits around for quite a while even if there are no branches or tags pointing to them.
Chloe Bennett explores the intersection of pop culture, streaming entertainment, digital trends, and contemporary lifestyle. Her weekly commentary reaches thousands of culture enthusiasts.
