How to Restore a Git Repository to a Previous Commit?

To restore a Git repository to a previous commit, you can use the git checkout command or the git reset command, depending on your objective. Below, I will provide a detailed explanation of both methods, along with practical examples.

Method 1: Using git checkout

If you simply want to temporarily inspect or use an older version without affecting the latest work on the current branch, you can use the git checkout command. This command allows you to switch to any historical commit.

Steps:

1. First, open the command line and navigate to your Git project directory.
2. Use git log to view the commit history and identify the hash value of the commit you want to restore.
3. Execute git checkout [commit-hash] to switch the repository to that commit. Here, [commit-hash] is the hash value identified in step 2.

Example:

bash
git log --oneline
git checkout 1a2b3c4

Method 2: Using git reset

If you need to reset the HEAD (the latest commit on the current branch), index, and working directory to a specific commit state, and you may need to continue development based on it, using git reset is more appropriate.

Steps:

1. Similarly, first view the commit history to identify the hash value of the target commit.
2. Use the git reset command with the appropriate options:
   • git reset --soft [commit-hash]: Reset to a specific commit without altering the working directory, but the index (staging area) will be reset to that point.
   • git reset --mixed [commit-hash]: Reset to a specific commit without altering the working directory, and the index will also be reset to that point (default option).
   • git reset --hard [commit-hash]: Completely reset to a specific commit, resetting both the working directory and index, which means all uncommitted changes will be lost.

Example:

bash
git log --oneline
git reset --hard 1a2b3c4

In practice, the choice of method depends on your specific needs. Using git checkout is a safe way to inspect older versions, while git reset is suitable for scenarios where you need to perform further operations on historical versions. Be particularly cautious when using git reset --hard as it may result in the loss of uncommitted changes. If unsure, you can first create a backup.