Version control concept (Git) in Intro to Computing - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to initialize a new Git repository.

Intro to Computing

git [1]

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

Ainit

Bcommit

Cclone

Dpush

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'commit' instead of 'init' which records changes but does not create a repo.

Using 'clone' which copies an existing repo, not creates a new one.

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

2fill in blank

medium

Complete the command to save changes to the local repository.

Intro to Computing

git [1] -m "Save changes"

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

Astatus

Bpush

Cpull

Dcommit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'push' which sends changes to a remote repository, not saving locally.

Using 'pull' which fetches changes from remote, not saving changes.

The git commit command saves your changes to the local repository with a message describing the changes.

3fill in blank

hard

Fix the error in the command to upload local commits to the remote repository.

Intro to Computing

git [1] origin main

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

Acommit

Bfetch

Cpush

Dclone

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'commit' which only saves locally.

Using 'clone' which copies a repo, not uploads changes.

The git push command uploads your local commits to the remote repository named 'origin' on the 'main' branch.

4fill in blank

hard

Fill both blanks to create a new branch and switch to it.

Intro to Computing

git [1] [2]

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

Acheckout

Bbranch

Cmerge

D-b

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'merge' which combines branches but does not create or switch.

Using 'status' which shows repo status but does not affect branches.

The command git checkout -b branch_name creates a new branch and switches to it. Here, checkout is used with -b option to create and switch branches.

5fill in blank

hard

Fill all three blanks to list all branches and show the current branch.

Intro to Computing

git [1] && git [2] -v && git [3]

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

Abranch

Bstatus

Clog

Ddiff

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'log' which shows commit history, not branches.

Using 'diff' which shows changes, not branch list.

The command git branch lists all branches and shows the current one with a star. The -v option shows last commit info. git status shows the current state of the working directory.

Practice

1. What is the main purpose of using version control systems like Git?

easy

A. To speed up the computer's processor

B. To create graphics and animations

C. To delete old files automatically

D. To save and track changes to files over time

Solution

1. Step 1: Understand version control basics

   Version control systems keep a history of changes made to files, allowing users to track and manage edits.

2. Step 2: Compare options to purpose

   Only To save and track changes to files over time describes saving and tracking changes, which matches the main purpose of Git.

3. Final Answer:

   To save and track changes to files over time -> Option D

4. Quick Check:

   Version control = save and track changes [OK]

Hint: Version control = saving drafts of your work [OK]

Common Mistakes:

• Confusing version control with speeding up hardware
• Thinking it deletes files automatically
• Assuming it creates graphics

2. Which Git command is used to start a new repository in your project folder?

easy

A. git init

B. git commit

C. git add

D. git push

Solution

1. Step 1: Identify command purpose

   git init creates a new Git repository in the current folder, starting version control.

2. Step 2: Check other commands

   git add stages files, git commit saves changes, and git push sends changes to a remote repository.

3. Final Answer:

   git init -> Option A

4. Quick Check:

   Start repo = git init [OK]

Hint: Initialize repo with git init command [OK]

Common Mistakes:

• Using git add to start a repo
• Confusing git commit with git init
• Thinking git push starts a repo

3. What will happen after running these commands in order?

git init
git add file.txt
git commit -m "First commit"

medium

A. file.txt is ignored by Git

B. A new repository is created and file.txt is saved in the first commit

C. The repository is deleted

D. file.txt is deleted from the folder

Solution

1. Step 1: Analyze each command

   git init creates a new repo, git add file.txt stages the file, and git commit saves the staged file as a commit.

2. Step 2: Understand the result

   The file is saved in the repository history as the first commit; nothing is deleted or ignored.

3. Final Answer:

   A new repository is created and file.txt is saved in the first commit -> Option B

4. Quick Check:

   Init + add + commit = save file in repo [OK]

Hint: Init, add, commit = save file snapshot [OK]

Common Mistakes:

• Thinking commit deletes files
• Confusing add with delete
• Assuming file is ignored automatically

4. You ran git commit -m "Update" but got an error saying "nothing to commit". What is the likely cause?

medium

A. You did not stage any files with git add

B. You forgot to run git init

C. You typed the commit message incorrectly

D. Your files are deleted

Solution

1. Step 1: Understand the error message

   "Nothing to commit" means Git sees no changes staged to save.

2. Step 2: Identify missing step

   Before committing, files must be staged with git add. Without staging, commit has nothing to save.

3. Final Answer:

   You did not stage any files with git add -> Option A

4. Quick Check:

   Commit needs staged files [OK]

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

Common Mistakes:

• Skipping git add before commit
• Assuming commit message typo causes this error
• Thinking files are deleted

5. You want to save changes to two files, index.html and style.css, but only index.html should be included in the commit. Which sequence of commands achieves this?

hard

A. git commit -m "Update index"

B. git add .
git commit -m "Update index"

C. git add index.html
git commit -m "Update index"

D. git add style.css
git commit -m "Update index"

Solution

1. Step 1: Stage only the desired file

   Using git add index.html stages only that file, excluding others.

2. Step 2: Commit staged changes

   git commit -m "Update index" saves only the staged index.html changes.

3. Final Answer:

   git add index.html git commit -m "Update index" -> Option C

4. Quick Check:

   Stage specific file, then commit [OK]

Hint: Add only files you want before commit [OK]

Common Mistakes:

• Using git add . to stage all files
• Committing without staging
• Adding wrong file by mistake