Home / Questions / 1458
Accepted
jasilva
Asked: 2020-12-22 08:56:14 +0800 CST 2020-12-22 08:56:14 +0800 CST

Return a repository to a specific commit

  • 772

Based on How can I undo the last commit in Git? .

Is there a way to return a Git repository to a specific commit?

For example:

  • commit to "First commit"
  • commit b
  • commit c
  • commit d
  • commit and
  • commit f
  • commit g
  • commit h "Current version"

Is there a way to return to "commit c"?

git

2 Answers

  1. Best Answer

    You just have to do git checkout commitCwhere commitCis the hash of said commit.

    Example:

    You look in the git log for the commit you want to return to:

    git log

    You will have something like this:

    commit eb9b03c2e22305c965b610aa84a7d316e5cb208d
Author: oscar <oscar@oscar.(none)>
Date:   Thu Sep 19 16:05:51 2013 +0200

    commit3

commit 96046152e2515d651d777bac66602e4a50654f49
Author: oscar <oscar@oscar.(none)>
Date:   Thu Sep 19 00:13:37 2013 +0200

    commit2

commit 23abd7d49c00541fcac17acb1babd7a60a3e7c6e
Author: oscar <oscar@oscar.(none)>
Date:   Wed Sep 18 23:53:25 2013 +0200

    commit1

    You can see more information about git log here.

    Then you do this:

    git checkout eb9b03c

    For more information about git checkout you can see here.

    Then you HEADwill be pointing to the commit3, being the result you need.

    • 35

  2. Solution

    Just run the following command (replace <hash>):

    $ git checkout <hash>

    Explanation

    To be able to jump from one confirmation (commit) to another, you must know the number (hash) by which it was registered. Taking into account that the official Git book in Spanish, section 2.3 Git Basics - Viewing the commit history , tells us:

    After you've made several commits, or if you've cloned a repository that already had a commit history, you'll probably want to look back to see what changes have been made. The most basic and powerful tool to do this is the git log.

    When executing the command git logon your project, you will have something similar to this:

    $ git log
commit ca82a6dff817ec66f44342007202690a93763949
Author: Scott Chacon <[email protected]>
Date:   Mon Mar 17 21:52:11 2008 -0700

    Cambiado el número de versión

commit 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7
Author: Scott Chacon <[email protected]>
Date:   Sat Mar 15 16:40:33 2008 -0700

    Removido código de prueba innecesario

commit a11bef06a3f659402fe7563abf99ad00de2209e6
Author: Scott Chacon <[email protected]>
Date:   Sat Mar 15 10:31:28 2008 -0700

    Primera confirmación

    The hash (or commit number) will be the alphanumeric set that is followed by the word commit . You will copy this hash to use it with the command git checkout <hash>that will be in charge of moving the HEAD pointer of your project to the indicated commit. Visual example (taking into account that you are the project is the branch master):

    git checkout example

    In this way we can perceive that although your pointer now points to a previous capture, your changes after it still exist.

    You can obtain more official information and in Spanish related to this topic in the following link: 6.1 Git tools - Selection of specific change commits

    Short SHA : By simply giving it the first few characters of the SHA-1 code, Git is smart enough to figure out what the desired commit is. It is necessary to type at least 4 characters and these must be unambiguous --that is, there must be a single object in the repository whose code begins with said initial part of the SHA--.

    • 17