Summary - Reflog

Combine the reflog flow to safely recover.

Safe recovery with reflog

Reflog helps you find previous HEAD positions after accidental resets or branch switches. First identify the correct commit with git reflog, then inspect its contents with git show. Protect the commit by creating a new branch so it does not become difficult to reach again.

git reflog
git show a1b2c3d
git branch recover a1b2c3d

After protecting the commit, you can switch to the recovery branch and continue your work.

Exercise Complete the recovery workflow

Use b7c8d9e as the example commit identifier. First point a new branch named safe to the commit, then inspect that branch's contents with git show, and finally switch to the branch. Complete the commands in the specified order.

Show example solution

# Commit'i koru
git branch guvenli b7c8d9e

# Dalın commit'ini incele
git show guvenli

# Kurtarma dalına geç
git switch guvenli

Test yourself

What is the safest first step during recovery?
- Find the commit in reflog and inspect it
- Run another reset --hard
- Delete all remote branches
- Delete the repository's .git directory
Show answer

Find the commit in reflog and inspect it — You should first identify the correct commit in reflog and inspect its contents. This reduces the risk of recovering the wrong commit.

Place the commit on a recovery branch

git branch guvenli ____

Show answer

git branch guvenli b7c8d9e

Safe recovery workflow

git reflog

Find the previous HEAD position
git show

Verify the commit contents
git branch

Protect the commit
git switch

Switch to the recovery branch

Next lesson: What is a PR?

We Are Enhancing Your Experience

Cookie Preferences

Strictly Necessary Cookies

Analytical Cookies