How files move between three areas in Git - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to add a file to the staging area.

Git

git [1] filename.txt

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

Aadd

Bcommit

Cpush

Dclone

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'commit' instead of 'add'

Using 'push' which sends changes to remote

The git add command moves files from the working directory to the staging area.

2fill in blank

medium

Complete the command to save staged changes to the local repository.

Git

git [1] -m "Save changes"

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

Apush

Bcommit

Cadd

Dstatus

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'add' instead of 'commit'

Using 'push' which sends changes to remote

The git commit command saves the staged changes to the local repository.

3fill in blank

hard

Fix the error in the command to send commits to the remote repository.

Git

git [1] origin main

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

Apush

Bcommit

Cadd

Dpull

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'commit' instead of 'push'

Using 'pull' which downloads changes

The git push command sends committed changes to the remote repository.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that maps files to their sizes only if size is greater than 1000.

Git

{filename: [1] for filename, size in files.items() if size [2] 1000}

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

Asize

B==

C>

D<

Attempts:

3 left

💡 Hint

Common Mistakes

Using '==' instead of '>'

Using '<' which selects smaller sizes

The comprehension maps each filename to its size if the size is greater than 1000.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps uppercase filenames to their sizes only if size is less than 5000.

Git

{filename[1]: size for filename, size in files.items() if size [2] 5000 and filename[3]('.txt')}

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

A.upper()

B<

C.endswith

D>

Attempts:

3 left

💡 Hint

Common Mistakes

Using '>' instead of '<' for size

Using '.startswith' instead of '.endswith'

The comprehension maps uppercase filenames to sizes if size is less than 5000 and filename ends with '.txt'.

Practice

1. Which command moves files from the working directory to the staging area in Git?

easy

A. git add

B. git commit

C. git push

D. git clone

Solution

1. Step 1: Understand the role of git add

   The git add command moves files from the working directory to the staging area, preparing them for commit.

2. Step 2: Differentiate from other commands

   git commit saves staged files to the local repository, git push sends commits to a remote, and git clone copies a repository.

3. Final Answer:

   git add -> Option A

4. Quick Check:

   Staging area update = git add [OK]

Hint: Add files to staging with git add [OK]

Common Mistakes:

• Confusing git add with git commit
• Thinking git push moves files locally
• Using git clone to stage files

2. Which of these commands correctly saves staged files to the local repository?

easy

A. git commit -m "Save changes"

B. git status

C. git add .

D. git init

Solution

1. Step 1: Identify the commit command

   git commit -m "message" saves the staged files into the local repository with a message.

2. Step 2: Understand other commands

   git add . stages files, git status shows status, and git init creates a new repo.

3. Final Answer:

   git commit -m "Save changes" -> Option A

4. Quick Check:

   Save staged files = git commit [OK]

Hint: Commit staged files with git commit -m [OK]

Common Mistakes:

• Using git add instead of git commit to save
• Confusing git status with commit
• Trying to commit without staging files

3. Given these commands run in order:

echo "Hello" > file.txt
git add file.txt
git commit -m "Add file"

Where is file.txt after these commands?

medium

A. Only in the working directory

B. In the local repository and working directory

C. Deleted from all areas

D. In the staging area only

Solution

1. Step 1: Create and stage the file

   The file is created in the working directory, then moved to the staging area by git add.

2. Step 2: Commit the file

   git commit saves the staged file to the local repository. The file remains in the working directory.

3. Final Answer:

   In the local repository and working directory -> Option B

4. Quick Check:

   Commit saves staged files, working files remain [OK]

Hint: Committed files stay in repo and working directory [OK]

Common Mistakes:

• Thinking commit removes file from working directory
• Believing staged files disappear after commit
• Confusing staging area with repository

4. You ran git commit -m "Update" but Git says "nothing to commit". What is the likely cause?

medium

A. You committed files but did not push

B. You are in the wrong directory

C. You forgot to stage files with git add

D. You need to run git init again

Solution

1. Step 1: Understand the message meaning

   "Nothing to commit" means no changes are staged for commit.

2. Step 2: Identify missing staging step

   If you forgot git add, no files are staged, so commit has nothing to save.

3. Final Answer:

   You forgot to stage files with git add -> Option C

4. Quick Check:

   Stage files before commit = git add [OK]

Hint: Stage files first with git add before commit [OK]

Common Mistakes:

• Thinking commit auto-stages files
• Confusing push with commit
• Assuming git init fixes this error

5. You edited app.js in your working directory. You want to save only this file to the local repository without including other changes. Which sequence of commands correctly moves app.js through Git's three areas?

hard

A. git add . then git commit -m "Save app.js"

B. git commit -m "Save app.js" then git add app.js

C. git push then git add app.js

D. git add app.js then git commit -m "Save app.js"

Solution

1. Step 1: Stage the specific file

   Use git add app.js to move only app.js to the staging area.

2. Step 2: Commit the staged file

   Run git commit -m "Save app.js" to save the staged changes to the local repository.

3. Final Answer:

   git add app.js then git commit -m "Save app.js" -> Option D

4. Quick Check:

   Stage then commit specific file = git add + git commit [OK]

Hint: Add specific file before commit to save only it [OK]

Common Mistakes:

• Committing before adding files
• Using git push instead of commit
• Adding all files instead of just one