Why recovery skills are critical in Git - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is it important to know how to recover lost commits in Git?

Imagine you accidentally deleted some commits in your Git repository. Why is it important to know how to recover them?

A Because lost commits can contain important work that might be hard to redo.

B Because Git automatically deletes all commits after 24 hours.

C Because recovering commits speeds up the computer performance.

D Because commits are only stored locally and cannot be pushed again.

💡 Hint

Think about what happens if you lose work you spent time on.

Lost commits may contain valuable changes. Knowing recovery helps avoid losing work and saves time.

💻 Command Output

intermediate

What is the output of 'git reflog' after resetting a branch?

After running git reset --hard HEAD~1, what does git reflog show?

Git

git reset --hard HEAD~1
git reflog

A Shows the previous HEAD positions including the reset commit.

B Shows only the current HEAD commit, no history.

C Shows an error because reflog is disabled by default.

D Shows the commit history from the remote repository.

💡 Hint

Reflog records where HEAD has been recently.

Reflog keeps track of all recent HEAD changes, including resets, allowing recovery.

🔀 Workflow

advanced

Which sequence correctly recovers a deleted branch in Git?

You accidentally deleted a branch named feature. Which sequence of commands will recover it?

A git reset --hard feature; git checkout feature

B git reflog; git checkout -b feature <commit-hash>

C git branch feature; git push origin feature

D git clone feature; git checkout feature

💡 Hint

Think about how to find the commit hash of the deleted branch.

Using git reflog helps find the last commit hash of the deleted branch, then git checkout -b recreates it.

❓ Troubleshoot

advanced

What error occurs if you try to recover a commit with a wrong hash?

You run git checkout -b fix . What error will Git show?

A error: branch 'fix' already exists

B error: cannot checkout detached HEAD

C fatal: not a git repository

D fatal: reference is not a tree: <wrong-hash>

💡 Hint

Think about what happens if the commit hash does not exist.

Git reports 'fatal: reference is not a tree' when the commit hash is invalid or not found.

✅ Best Practice

expert

What is the best practice to avoid losing work in Git?

Which practice helps prevent losing commits accidentally?

A Delete old branches immediately after merging without backup.

B Only work on the main branch and avoid pushing until the project is finished.

C Regularly push commits to a remote repository and use branches for features.

D Use <code>git reset --hard</code> frequently to clean history.

💡 Hint

Think about how backups and isolation help protect work.

Pushing to remote and using branches isolates work and creates backups, reducing risk of loss.