Why branches are essential in Git - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new branch named 'feature'.

Git

git branch [1]

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

Amaster

Bfeature

Cmain

Ddevelop

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'main' or 'master' creates or switches to existing branches, not new feature branches.

The command git branch feature creates a new branch called 'feature'.

2fill in blank

medium

Complete the command to switch to the 'feature' branch.

Git

git [1] feature

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

Acheckout

Bcommit

Cmerge

Dbranch

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'branch' only lists or creates branches, it does not switch.

The command git checkout feature switches your working directory to the 'feature' branch.

3fill in blank

hard

Fix the error in the command to merge 'feature' into 'main'.

Git

git [1] feature

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

Acheckout

Bbranch

Ccommit

Dmerge

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'checkout' or 'branch' instead of 'merge' causes errors or wrong actions.

The correct command to combine changes from 'feature' into 'main' is git merge feature while on 'main' branch.

4fill in blank

hard

Fill both blanks to create and switch to a new branch named 'bugfix'.

Git

git [1] -b [2]

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

Acheckout

Bbranch

Cfeature

Dbugfix

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'branch' with '-b' is invalid; '-b' is used with 'checkout'.

The command git checkout -b bugfix creates and switches to the 'bugfix' branch in one step.

5fill in blank

hard

Fill all three blanks to delete a local branch named 'oldfeature'.

Git

git [1] -[2] [3]

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

Abranch

Bd

Coldfeature

Dcheckout

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'checkout' instead of 'branch' will cause errors.

The command git branch -d oldfeature deletes the local branch named 'oldfeature'.

Practice

1. Why are branches important in Git?
git branch feature creates a new branch. What is the main reason to use branches?

easy

A. To work on new features without affecting the main code

B. To delete files from the project

C. To speed up the computer

D. To permanently remove old versions

Solution

1. Step 1: Understand what branches do

   Branches let you create a separate copy of the project to work on changes safely.

2. Step 2: Identify the main purpose of branches

   Branches help keep new work separate so the main project stays stable.

3. Final Answer:

   To work on new features without affecting the main code -> Option A

4. Quick Check:

   Branches isolate work = A [OK]

Hint: Branches isolate new work from main code [OK]

Common Mistakes:

• Thinking branches delete files
• Believing branches speed up the computer
• Confusing branches with deleting old versions

2. Which Git command correctly creates a new branch named dev?

easy

A. git create branch dev

B. git branch dev

C. git new dev

D. git start branch dev

Solution

1. Step 1: Recall Git branch creation syntax

   The correct command to create a branch is git branch branch_name.

2. Step 2: Match the command with options

   Only git branch dev matches the correct syntax.

3. Final Answer:

   git branch dev -> Option B

4. Quick Check:

   Correct branch command = C [OK]

Hint: Use 'git branch <branch_name>' to create branches [OK]

Common Mistakes:

• Using 'git create branch' which is invalid
• Trying 'git new' which is not a Git command
• Using 'git start branch' which does not exist

3. What will be the output of the following commands?

git branch
git checkout -b feature1
git branch

medium

A. * master\n feature1

B. feature1\n* master

C. * feature1\n master

D. master\n* feature1

Solution

1. Step 1: Understand initial branch list

   First git branch shows * master (assuming on master).

2. Step 2: Analyze git checkout -b feature1

   This creates and switches to feature1 branch, so next git branch shows * feature1 as current.

3. Step 3: Check output order

   Branches are listed in the order they were created, so master then feature1. The star (*) marks current branch.

4. Final Answer:

   master\n* feature1 -> Option D

5. Quick Check:

   Current branch marked * = B [OK]

Hint: Star (*) marks current branch in 'git branch' output [OK]

Common Mistakes:

• Confusing which branch is current
• Mixing order of branches in output
• Ignoring the star (*) symbol

4. You ran git checkout feature but got an error: error: pathspec 'feature' did not match any file(s) known to git. What is the likely problem?

medium

A. The branch 'feature' does not exist yet

B. You have uncommitted changes blocking checkout

C. You typed the command in the wrong folder

D. Git is not installed properly

Solution

1. Step 1: Understand the error message

   The error says the branch name 'feature' is unknown to Git, meaning it does not exist.

2. Step 2: Identify the cause

   Trying to checkout a branch that was never created causes this error.

3. Final Answer:

   The branch 'feature' does not exist yet -> Option A

4. Quick Check:

   Unknown branch error = D [OK]

Hint: Check if branch exists before checkout [OK]

Common Mistakes:

• Assuming uncommitted changes cause this error
• Thinking Git installation is broken
• Ignoring the branch name spelling

5. You want to add a new feature without disturbing the main project. Which sequence of commands correctly uses branches to do this safely?

hard

A. git merge new-featuregit branch new-featuremake changesgit commit -m 'Add feature'

B. git checkout mainmake changesgit commit -m 'Add feature'git branch new-featuregit merge main

C. git branch new-featuregit checkout new-featuremake changesgit commit -m 'Add feature'git checkout maingit merge new-feature

D. git commit -m 'Add feature'git branch new-featuregit checkout new-featuregit merge main

Solution

1. Step 1: Create and switch to a new branch

   Use git branch new-feature then git checkout new-feature to isolate work.

2. Step 2: Make changes and commit on new branch

   Make your changes and commit them safely on new-feature.

3. Step 3: Switch back and merge changes

   Switch to main and merge new-feature to add the feature safely.

4. Final Answer:

   git branch new-feature
   git checkout new-feature
   make changes
   git commit -m 'Add feature'
   git checkout main
   git merge new-feature -> Option C

5. Quick Check:

   Branch, commit, merge sequence = A [OK]

Hint: Create branch, commit changes, then merge back [OK]

Common Mistakes:

• Committing on main before branching
• Merging before making changes
• Switching branches in wrong order