What’s the difference between “git reset” and “git checkout”?

  • git reset is specifically about updating the index, moving the HEAD.
  • git checkout is about updating the working tree (to the index or the specified tree). It will update the HEAD only if you checkout a branch (if not, you end up with a detached HEAD).
    (actually, with Git 2.23 Q3 2019, this will be git restore, not necessarily git checkout)

By comparison, since svn has no index, only a working tree, svn checkout will copy a given revision on a separate directory.
The closer equivalent for git checkout would:

  • svn update (if you are in the same branch, meaning the same SVN URL)
  • svn switch (if you checkout for instance the same branch, but from another SVN repo URL)

All those three working tree modifications (svn checkout, update, switch) have only one command in git: git checkout.
But since git has also the notion of index (that “staging area” between the repo and the working tree), you also have git reset.


Thinkeye mentions in the comments the article “Reset Demystified “.

For instance, if we have two branches, ‘master‘ and ‘develop‘ pointing at different commits, and we’re currently on ‘develop‘ (so HEAD points to it) and we run git reset master, ‘develop‘ itself will now point to the same commit that ‘master‘ does.

On the other hand, if we instead run git checkout master, ‘develop‘ will not move, HEAD itself will. HEAD will now point to ‘master‘.

So, in both cases we’re moving HEAD to point to commit A, but how we do so is very different. reset will move the branch HEAD points to, checkout moves HEAD itself to point to another branch.

http://git-scm.com/images/reset/reset-checkout.png

On those points, though:

LarsH adds in the comments:

The first paragraph of this answer, though, is misleading: “git checkout … will update the HEAD only if you checkout a branch (if not, you end up with a detached HEAD)”.
Not true: git checkout will update the HEAD even if you checkout a commit that’s not a branch (and yes, you end up with a detached HEAD, but it still got updated).

git checkout a839e8f updates HEAD to point to commit a839e8f.

De Novo concurs in the comments:

@LarsH is correct.
The second bullet has a misconception about what HEAD is in will update the HEAD only if you checkout a branch.
HEAD goes wherever you are, like a shadow.
Checking out some non-branch ref (e.g., a tag), or a commit directly, will move HEAD. Detached head doesn’t mean you’ve detached from the HEAD, it means the head is detached from a branch ref, which you can see from, e.g., git log --pretty=format:"%d" -1.

  • Attached head states will start with (HEAD ->,
  • detached will still show (HEAD, but will not have an arrow to a branch ref.

Leave a Comment