Creating a worktree in Git - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to create a new worktree named 'feature' based on the branch 'develop'.

Git

git worktree add [1] develop

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

Aorigin

Bfeature

Cmaster

Dmain

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong directory name like 'master' or 'main' when the branch is 'develop'.

Confusing the branch name with the directory name.

The git worktree add command creates a new working tree. Here, feature is the directory name for the new worktree based on the develop branch.

2fill in blank

medium

Complete the command to list all existing worktrees.

Git

git worktree [1]

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

Alist

Bshow

Cstatus

Dcheck

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'show' or 'status' which are not valid subcommands for 'git worktree'.

Confusing with other git commands like 'git status'.

The command git worktree list shows all the worktrees currently linked to the repository.

3fill in blank

hard

Fix the error in the command to remove a worktree located at 'feature'.

Git

git worktree [1] feature

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

Aremove-worktree

Bdelete

Cremove

Dprune

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'prune' which does not take a path argument and is for cleaning up non-existent worktrees.

Using 'delete' which is not a valid git worktree subcommand.

The correct command to remove a worktree is git worktree remove feature. It removes the working tree and its administrative files. Use -f to force removal if the worktree has uncommitted changes or untracked files.

4fill in blank

hard

Fill both blanks to create a new worktree named 'hotfix' based on a new branch 'hotfix-1.0'.

Git

git worktree add -b [1] [2]

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

Ahotfix-1.0

Bhotfix

Dmain

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping branch name and directory name.

Using the wrong branch name or directory.

The -b option creates a new branch named hotfix-1.0. The directory for the worktree is hotfix.

5fill in blank

hard

Fill all three blanks to create a worktree for branch 'release' in directory 'release-dir' and then switch to it.

Git

git worktree add [1] [2]
git -C [3] switch release

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

Arelease-dir

Brelease

Dmain

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up branch and directory names.

Forgetting to specify the directory in the switch command.

The first blank is the directory name release-dir, the second is the branch release, and the third is the directory to switch inside release-dir.

Practice

1. What is the main purpose of creating a Git worktree?

easy

A. To work on multiple branches simultaneously in separate folders

B. To merge two branches automatically

C. To delete a branch safely

D. To compress the repository size

Solution

1. Step 1: Understand what a worktree is

   A Git worktree allows you to have multiple working directories linked to the same repository.

2. Step 2: Identify the main use case

   This lets you work on different branches at the same time without switching branches in one folder.

3. Final Answer:

   To work on multiple branches simultaneously in separate folders -> Option A

4. Quick Check:

   Worktree = multiple branches, multiple folders [OK]

Hint: Worktrees = multiple branches open in separate folders [OK]

Common Mistakes:

• Thinking worktree merges branches
• Confusing worktree with branch deletion
• Believing worktree compresses repo

2. Which of the following is the correct syntax to create a new worktree for branch feature in folder ../feature-folder?

easy

A. git worktree add ../feature-folder feature

B. git worktree create feature ../feature-folder

C. git add worktree feature ../feature-folder

D. git worktree new ../feature-folder feature

Solution

1. Step 1: Recall the correct command structure

   The command to add a worktree is git worktree add <path> <branch>.

2. Step 2: Match the syntax with options

   git worktree add ../feature-folder feature matches the correct syntax exactly.

3. Final Answer:

   git worktree add ../feature-folder feature -> Option A

4. Quick Check:

   git worktree add path branch = correct syntax [OK]

Hint: Remember: 'git worktree add path branch' is correct syntax [OK]

Common Mistakes:

• Using 'create' instead of 'add'
• Swapping branch and path order
• Using 'git add worktree' which is invalid

3. Given the commands:

git worktree add ../test-branch test
cd ../test-branch
git branch --show-current

What will be the output of the last command?

medium

A. master

B. main

C. test

D. detached HEAD

Solution

1. Step 1: Understand what 'git worktree add' does

   This command creates a new folder with the specified branch checked out.

2. Step 2: Check current branch in new worktree

   After changing directory, git branch --show-current shows the branch name checked out, which is 'test'.

3. Final Answer:

   test -> Option C

4. Quick Check:

   Worktree folder shows branch name = test [OK]

Hint: Worktree folder shows the branch you added [OK]

Common Mistakes:

• Assuming default branch 'main' or 'master'
• Thinking it shows detached HEAD
• Confusing branch names

4. You run git worktree add ../new-feature without specifying a branch. What will happen?

medium

A. Git creates a new worktree with the current branch checked out

B. Git creates a new branch automatically

C. Git throws an error asking for a branch name

D. Git creates a detached HEAD worktree at the current commit

Solution

1. Step 1: Check behavior when branch is omitted

   If no branch is specified, Git creates a worktree at the current commit in detached HEAD state.

2. Step 2: Understand the result

   This means the worktree is not on any branch but on a specific commit.

3. Final Answer:

   Git creates a detached HEAD worktree at the current commit -> Option D

4. Quick Check:

   No branch given = detached HEAD worktree [OK]

Hint: No branch? Worktree is detached HEAD at current commit [OK]

Common Mistakes:

• Expecting an error without branch
• Thinking it uses current branch name
• Assuming a new branch is created

5. You want to work on two branches, main and feature, simultaneously. Your repo has no feature branch yet. Which sequence correctly creates a worktree for feature and switches to it?

hard

A. git worktree add ../feature feature
cd ../feature

B. git branch feature
git worktree add ../feature feature
cd ../feature

C. git worktree add ../feature feature
cd ../feature
git checkout -b feature

D. git checkout -b feature
git worktree add ../feature feature
cd ../feature

Solution

1. Step 1: Create the branch before adding worktree

   You must create the branch 'feature' first because it does not exist yet.

2. Step 2: Add the worktree for the new branch and switch directory

   Then add the worktree pointing to 'feature' and change to that folder.

3. Final Answer:

   git branch feature git worktree add ../feature feature cd ../feature -> Option B

4. Quick Check:

   Create branch first, then add worktree [OK]

Hint: Create branch first, then add worktree for it [OK]

Common Mistakes:

• Adding worktree before branch exists
• Creating branch inside worktree folder
• Forgetting to switch directory