Resetting, Checking Out, and Reverting - Atlassian. When in detached head state, also issue commands: git checkout master git pull. Reverting to Specifi Commit Based on Commit ID with Git - git fetch origin git reset -hard origin/master. To hard reset the remote repository, first hard reset the local and then run git push -f.Perform the local hard reset by running git reset -hard.Find the commit hash of the commit you want to reset to with git log.Only do a hard reset if you are the only using the remote repository, or if you haven't yet pushed the commits you're going to drop.In the example we used above, that git command would look like this: After you've reset the local repository, simply do a force push with the follow git command: Performing a hard reset of the remote repository is quite easy. You can see from git log and the Working Directory that we have rolled back to the second commit and dropped the third and fourth commits. Then, you would write down or copy the commit hash for that commit and run:īased on the example, that command would look like this:Īfter running the hard reset command, the Working Directory now looks like this: Let's say that after looking through this commit history you wanted to reset to the "second commit". To reset your local repository, first you need to know which commit you want to reset to, and what the hash is for that commit. So, after four commits I ended up with a README that looked like this: To simplify the example, I created a repository with a README in it, and for each commit, I added a line that matches the commit message. This means that any uncommitted work in the Staging Index or Work Directory will be lost. Just make sure you want drop the commits in question before you do the reset.Īlso, just as a quick reminder, git reset -hard will move the HEAD pointer back to the commit hash that was given, the Stage Index and the Working Directory will be reset back to the way they were at that commit, and all commits after the commit that was given will be dropped from the commit history. In this case, you're the only one affected by the hard reset, so it's relatively safe to do.
If another developer pulls and starts basing their work on the commits that the reset removes from the commit history, you're going to create huge problems.Ī hard reset can be done if you're the only one using the local and remote repository, or if the reset removes commits that have not yet been pushed to a shared remote. Git reset hard and remove all untracked files and directories This cmd will reset our branch and remove all untracked files and directories (non-ignored.
#Git reset head how to
Before we go over how to do this, let's go over when you should and should not do this.ĭon't do a hard reset if you've already pushed the commits in question to a shared remote repository.
0 kommentar(er)
