Listing worktrees in Git - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a Git worktree?

A Git worktree is an additional working directory linked to the same Git repository. It lets you work on multiple branches at the same time without switching branches in one folder.

beginner

Which command lists all Git worktrees?

The command git worktree list shows all the worktrees connected to the repository, including their paths and the branches checked out.

intermediate

What information does git worktree list display?

It shows the path of each worktree, the branch or commit checked out there, and if the worktree is locked or not.

intermediate

How can you identify the main worktree in the list?

The main worktree is usually the one with the repository root path and no special lock status. It is the original working directory of the repo.

beginner

Why use multiple worktrees instead of branches in one folder?

Multiple worktrees let you work on different branches at the same time without switching or losing changes. It’s like having multiple copies of your project linked to the same history.

Which command shows all Git worktrees?

A git status

B git branch -a

C git checkout

D git worktree list

The command git worktree list lists all worktrees connected to the repository.

What does a Git worktree allow you to do?

A Work on multiple branches at the same time

B Delete branches permanently

C Merge branches automatically

D Clone a repository

A Git worktree lets you have multiple working directories for different branches simultaneously.

In the output of git worktree list, what does the path represent?

A The commit hash

B The remote repository URL

C The location of the worktree directory

D The branch name only

The path shows where the worktree folder is located on your computer.

How do you know which worktree is the main one?

A It is always named 'main'

B It has the root repository path and no lock status

C It is the newest worktree

D It is locked

The main worktree is the original repo folder, usually unlocked and at the root path.

What happens if you delete a worktree folder without removing it from Git?

A Git still thinks the worktree exists and may cause errors

B Git automatically removes it

C Nothing, it is safe

D The branch is deleted

Deleting a worktree folder without telling Git can cause confusion and errors.

Explain what a Git worktree is and why you might use multiple worktrees.

Think about having multiple project folders linked to the same Git history.

Describe how to list all worktrees in a Git repository and what information you get from the list.

Focus on the command and the details it shows.