Debugging & Troubleshooting - Quiz

List files that still have merge conflicts after a failed merge

Create a new branch to preserve work done in a detached HEAD state

Undo the last commit but keep all its changes staged for another commit

Check the integrity of all objects in the current repository

Track all .psd design files with Git LFS in the current repository

Which situation most commonly leads to a merge conflict?

What is the main risk of working in a detached HEAD state?

Which command is best when you need to undo a public commit without rewriting history?

What does git gc primarily do?

Why use Git LFS for large binary assets?

Order the steps to resolve a merge conflict in file.txt and complete the merge.

Drag and drop to reorder, or use the arrows.

Order the steps to recover a deleted local branch using the reflog.

Drag and drop to reorder, or use the arrows.

Order the steps to clean up stale remote branches locally.

Drag and drop to reorder, or use the arrows.

Order the steps to start using Git LFS for .mp4 files in an existing repository.

Drag and drop to reorder, or use the arrows.

HEAD is currently at commit abc1234 on branch feature-login. What does this command print?

1git rev-parse --short HEAD

You are on branch hotfix-123. What does this command print?

1git branch --show-current

You have an unpushed local commit on main. What does this command print?

1git rev-parse --abbrev-ref HEAD

Your repository has a valid object database with no corruption. What does this command print?

1git rev-parse --git-dir

Find the incorrect command in this attempt to undo and then recover a hard reset.

Click on the line(s) that contain the bug.

git reset --hard HEAD~1

git reflog

git checkout recovered-branch <hash-from-reflog>

git checkout -b recovered-branch <hash-from-reflog>

Identify the incorrect step in this workflow to clean up large files using filter-repo.

Click on the line(s) that contain the bug.

git filter-repo --path-large-file.bin --invert-paths

git push origin main

git push --force-with-lease origin main

Spot the mistake in this attempt to resolve a merge conflict and finish the merge.

Click on the line(s) that contain the bug.

git status

git add conflicted-file.txt

git merge --continue

git commit -m "Finish merge"

Match each Git concept to its description.

Click an item on the left, then click its match on the right. Click a matched item to unmatch.

Match Git commands to their use in fixing mistakes.

Click an item on the left, then click its match on the right. Click a matched item to unmatch.

Match the Git LFS and large-file tools to their purposes.

Click an item on the left, then click its match on the right. Click a matched item to unmatch.

Complete the commands to safely recover a deleted branch using its last known commit from reflog.

Complete the commands to clean up unreachable objects after verifying them with fsck.

Complete the commands to avoid committing large video files by default.

Click the line that indicates a merge conflict in app.js.

Click on the line to select.

On branch feature-ui

You have unmerged paths.

  (fix conflicts and run "git commit")

Unmerged paths:

  (use "git add <file>..." to mark resolution)

	both modified:   app.js

no changes added to commit (use "git add" and/or "git commit -a")

Click the line showing that HEAD is detached at a specific commit.

Click on the line to select.

Note: switching to '83a1b2c'.

You are in 'detached HEAD' state.

You can look around, make experimental changes and commit them,

and you can discard any commits you make in this state without impacting any branches by switching back to a branch.

HEAD is now at 83a1b2c Fix critical bug

Click the line that shows an unreachable blob reported by git fsck.

Click on the line to select.

$ git fsck

unreachable blob b4c3d2e0c3de9b83a4dbb3e9e2f6d2a3b0c9e3f2

dangling commit 0d4c9d2c5e3f2c9e5d3c2c4e9b1e3d2c4d1e2b3