How can I rollback a git repository to a specific commit?

When using Git, if you need to reset your repository to a specific commit, you can follow these steps:

1. Find the hash of the target commit: First, determine the specific commit you want to reset to. You can view the commit history using the git log command to find the hash of the target commit. For example:

   bash
   git log --oneline

   This will display a concise commit history along with the hash of each commit.

2. Use git reset to reset to the specified commit: After identifying the hash of the target commit, you can use the git reset command to move the HEAD pointer (which points to the current branch) to that commit. There are several ways to use this command:

   • git reset --hard <commit-hash>: This command resets both the working directory and staging area to match the specified commit exactly. Note that this will lose all uncommitted changes.
   • git reset --soft <commit-hash>: This command only moves the HEAD pointer but leaves the staging area and working directory unchanged. This allows you to re-stage and commit these changes.
   • git reset --mixed <commit-hash>: This is the default option. It resets the HEAD to the specified commit and resets the staging area, but does not alter the working directory. You can selectively re-add changes to the staging area.

   Example command:

   bash
   git reset --hard 1a2b3c4d

3. Push changes to the remote repository: If you have already pushed changes to the remote repository, you must use the --force option to force-push, as this is a history rewrite operation:

   bash
   git push origin <branch-name> --force

   Using the --force option requires caution because it will overwrite the history in the remote repository, potentially affecting other collaborators' work.

In practical scenarios, for instance, in a previous project, we needed to reset to a stable version due to severe bugs introduced by subsequent changes. I used the git reset --hard command to revert to that stable commit and then pushed the changes to the main branch using git push --force. This ensured our production environment returned to normal quickly. While this operation is powerful, it requires careful handling to avoid unnecessary data loss.