Reflog for finding lost commits in Git - Mini Project: Build & Apply

Reflog for Finding Lost Commits

📖 Scenario: You are working on a project using Git. Sometimes, you might accidentally lose track of commits after resetting or switching branches. Git keeps a hidden log called reflog that records all changes to the HEAD pointer. This helps you find lost commits and recover them.

🎯 Goal: Learn how to use git reflog to find lost commits and restore them by creating a new branch pointing to the lost commit.

📋 What You'll Learn

Use git reflog to view recent HEAD changes

Identify the commit hash of a lost commit from reflog output

Create a new branch pointing to the lost commit hash

Verify the lost commit is restored by checking the branch log

💡 Why This Matters

🌍 Real World

Developers often accidentally lose commits when resetting branches or switching contexts. Reflog helps find and restore these commits, preventing data loss.

💼 Career

Knowing how to use reflog is essential for developers and DevOps engineers to recover lost work and maintain code integrity in real projects.

1

View the reflog to see recent HEAD changes

Run the command git reflog to display the recent changes to the HEAD pointer, including lost commits.

Git

# Run the command to view reflog
# Your code here

Need a hint?

Type git reflog exactly to see the history of HEAD movements.

2

Identify the commit hash of the lost commit

Look at the output of git reflog and copy the commit hash (a string of letters and numbers) of the lost commit you want to recover. Assign this hash as a string to a variable called lost_commit in your shell or script.

Git

git reflog

# Assign the lost commit hash to variable lost_commit
# Your code here

Need a hint?

Copy the commit hash from reflog output and assign it like lost_commit="commit_hash_here".

3

Create a new branch pointing to the lost commit

Use the command git branch recovered_branch $lost_commit to create a new branch called recovered_branch that points to the lost commit hash stored in lost_commit.

Git

git reflog
lost_commit="a1b2c3d4e5f67890"

# Create a new branch called recovered_branch at lost_commit
# Your code here

Need a hint?

Use git branch recovered_branch $lost_commit to restore the lost commit as a branch.

4

Verify the recovered branch points to the lost commit

Run git log recovered_branch -1 --oneline to display the latest commit on recovered_branch and confirm it matches the lost commit hash.

Git

git reflog
lost_commit="a1b2c3d4e5f67890"
git branch recovered_branch $lost_commit

# Show the latest commit on recovered_branch
# Your code here

Need a hint?

The output should show the lost commit hash and its message.