What is Git - Interactive Quiz & Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to check the current Git version.

Git

git [1]

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

Acommit

Bclone

Cpush

D--version

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'commit' instead of '--version' will try to make a commit.

Using 'push' or 'clone' are for other Git actions, not version info.

The git --version command shows the installed Git version.

2fill in blank

medium

Complete the command to create a new Git repository in the current folder.

Git

git [1]

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

Aclone

Binit

Cadd

Dstatus

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'clone' tries to copy an existing repository instead.

Using 'status' only shows the current state of files.

The git init command creates a new Git repository in your current folder.

3fill in blank

hard

Fix the error in the command to check the status of files in Git.

Git

git [1]

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

Astatus

Bstat

Cstash

Dstage

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'stat' causes an error because it is not a Git command.

Using 'stash' saves changes temporarily, not shows status.

The correct command to see file changes is git status. 'stat' is not a Git command.

4fill in blank

hard

Fill both blanks to add all files and commit with a message.

Git

git [1] . && git [2] -m "Initial commit"

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

Aadd

Bcommit

Cpush

Dclone

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'push' instead of 'commit' tries to send changes to remote.

Using 'clone' is for copying repositories, not committing.

git add . stages all files, and git commit -m "message" saves the changes with a message.

5fill in blank

hard

Fill all three blanks to clone a repository, change directory, and check status.

Git

git [1] https://github.com/user/repo.git && cd [2] && git [3]

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

Aclone

Brepo

Cstatus

Dinit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'init' instead of 'clone' does not copy remote repo.

Using wrong folder name after cd causes errors.

git clone copies the repo, cd repo moves into it, and git status shows file changes.

Practice

1. What is the main purpose of Git?

easy

A. To create websites from scratch

B. To edit images and videos

C. To save and track changes in files over time

D. To manage computer hardware settings

Solution

1. Step 1: Understand Git's role

   Git is a tool designed to save and track changes in files, especially code files.

2. Step 2: Compare options

   Options B, C, and D describe tasks unrelated to Git's main function.

3. Final Answer:

   To save and track changes in files over time -> Option C

4. Quick Check:

   Git = tracks file changes [OK]

Hint: Git tracks file changes, not edits or hardware [OK]

Common Mistakes:

• Confusing Git with editing software
• Thinking Git manages hardware
• Believing Git builds websites

2. Which of the following is the correct command to start a new Git repository?

easy

A. git start

B. git init

C. git create

D. git begin

Solution

1. Step 1: Recall Git commands

   The command to create a new Git repository is git init.

2. Step 2: Check other options

   Commands like git start, git create, and git begin do not exist in Git.

3. Final Answer:

   git init -> Option B

4. Quick Check:

   Initialize repo = git init [OK]

Hint: Use 'git init' to start a repo, others are invalid [OK]

Common Mistakes:

• Using 'git start' instead of 'git init'
• Confusing command names
• Trying commands that don't exist

3. What will be the output of the command git status right after running git init in a new folder?

medium

A. No commits yet, nothing to commit, working tree clean

B. Error: repository not found

C. All files are staged for commit

D. Untracked files present, please add them

Solution

1. Step 1: Understand 'git init' effect

   Running git init creates an empty Git repository with no commits.

2. Step 2: Check 'git status' output

   Right after init, git status shows "No commits yet" and "working tree clean" because no files are added or changed.

3. Final Answer:

   No commits yet, nothing to commit, working tree clean -> Option A

4. Quick Check:

   git status after init = no commits, clean [OK]

Hint: After init, status shows no commits and clean tree [OK]

Common Mistakes:

• Expecting errors after init
• Thinking files are staged automatically
• Assuming untracked files message appears immediately

4. You ran git add file.txt but forgot to commit. What will git status show?

medium

A. Changes to be committed: new file: file.txt

B. No changes detected

C. Untracked files: file.txt

D. Error: file.txt not found

Solution

1. Step 1: Understand 'git add' effect

   Running git add file.txt stages the file for commit but does not commit it yet.

2. Step 2: Check 'git status' after add

   git status will show the file under "Changes to be committed" because it is staged.

3. Final Answer:

   Changes to be committed: new file: file.txt -> Option A

4. Quick Check:

   git add stages files, status shows staged changes [OK]

Hint: Added files show as staged, not committed yet [OK]

Common Mistakes:

• Thinking add commits files
• Expecting untracked files after add
• Assuming no changes after add

5. You want to save your changes permanently in Git. Which sequence of commands should you run?

hard

A. git init then git push

B. git commit -m "message" then git add .

C. git status then git push

D. git add . then git commit -m "message"

Solution

1. Step 1: Stage changes with 'git add'

   You first use git add . to stage all changes in the current folder.

2. Step 2: Commit staged changes

   Then run git commit -m "message" to save the staged changes permanently with a message.

3. Final Answer:

   git add . then git commit -m "message" -> Option D

4. Quick Check:

   Stage then commit = add then commit [OK]

Hint: Always add before commit to save changes [OK]

Common Mistakes:

• Committing before adding files
• Using push without commit
• Initializing repo unnecessarily