git diff for working directory changes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to see changes in the working directory compared to the index.

Git

git [1]

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

Astatus

Blog

Ccommit

Ddiff

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'git status' which shows file states but not detailed changes.

Using 'git log' which shows commit history, not file changes.

The git diff command shows the changes in your working directory compared to the index.

2fill in blank

medium

Complete the command to see changes only for a specific file named 'app.py'.

Git

git diff [1]

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

Aapp.py

B--staged

C--cached

DHEAD

Attempts:

3 left

💡 Hint

Common Mistakes

Using '--staged' or '--cached' which show staged changes, not working directory changes.

Using 'HEAD' which compares to last commit but not limited to one file.

Adding the filename after git diff shows changes only for that file.

3fill in blank

hard

Fix the error in the command to show staged changes for all files.

Git

git [1] --staged

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

Astatus

Bdiff

Ccommit

Dpush

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'git status --staged' which is invalid.

Confusing staged and unstaged changes.

The --staged option does not work with git status. To see staged changes, use git diff --staged. But here, the command is incorrect because git status --staged is invalid. The correct command to see staged changes is git diff --staged. So the error is using git status with --staged.

4fill in blank

hard

Fill both blanks to show changes between the working directory and the last commit for the file 'README.md'.

Git

git [1] [2] README.md

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

Adiff

Bstatus

CHEAD

Dcommit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'git status HEAD README.md' which is invalid.

Using 'git diff commit README.md' which is not a valid reference.

The command git diff HEAD README.md shows changes in 'README.md' between the working directory and the last commit.

5fill in blank

hard

Fill all three blanks to create a command that shows staged changes for all files.

Git

git [1] [2] [3]

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

Adiff

B--staged

C--cached

Dstatus

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'git status --staged --cached' which is invalid.

Using only one option instead of both.

The command git diff --staged --cached is redundant but valid to show staged changes. Usually, either --staged or --cached is used with git diff.