Why diffing matters in Git - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the command to see changes between your working directory and the staging area.

Git

git [1]

Drag options to blanks, or click blank then click option'

Astatus

Blog

Cdiff

Dcommit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'git status' instead of 'git diff' to see changes.

The git diff command shows the differences between your current files and the staging area.

2fill in blank

medium

Complete the command to compare changes between two commits.

Git

git diff [1] [2]

Drag options to blanks, or click blank then click option'

AHEAD

Bbranch

Ccommit2

Dcommit1

Attempts:

3 left

💡 Hint

Common Mistakes

Using branch names without specifying commits.

To compare two commits, you specify their IDs after git diff. Here, you start with the first commit ID.

3fill in blank

hard

Fix the error in the command to show changes staged for the next commit.

Git

git diff --[1]

Drag options to blanks, or click blank then click option'

Aadded

Bstaged

Ccommit

Dcached

Attempts:

3 left

💡 Hint

Common Mistakes

Using '--staged' which is not a valid git option.

The correct option to see staged changes is --cached. It shows what is ready to be committed.

4fill in blank

hard

Fill both blanks to create a diff of changes between the current branch and the main branch.

Git

git diff [1] [2]

Drag options to blanks, or click blank then click option'

Amain

Bmaster

CHEAD

Dorigin

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'origin' instead of branch names.

HEAD refers to your current branch, and main is the main branch. This command compares your current work with main.

5fill in blank

hard

Fill all three blanks to create a diff that shows changes introduced by the last commit.

Git

git diff [1]~1 [2] -- [3]

Drag options to blanks, or click blank then click option'

AHEAD

C.

Dmaster

Attempts:

3 left

💡 Hint

Common Mistakes

Using branch names instead of HEAD references.

This command compares the previous commit (HEAD~1) with the last commit (HEAD) and limits the diff to the current directory (.).