Listing worktrees in Git - Step-by-Step Execution

Process Flow - Listing worktrees

Run 'git worktree list'

↓

Git reads .git/worktrees directory

↓

Git gathers info on each worktree

↓

Git outputs list with paths and HEAD info

↓

Display result

The command reads the worktrees info and shows a list of all linked worktrees with their paths and current branch or commit.

Execution Sample

Git

git worktree list

Lists all worktrees linked to the current repository with their paths and HEAD states.

Process Table

Step	Action	Git Internal Process	Output
1	User runs 'git worktree list'	Git starts reading worktree info
2	Git reads .git/worktrees directory	Finds all linked worktrees
3	Git reads HEAD info for each worktree	Gets current branch or commit for each
4	Git formats list output	Prepares path and HEAD info lines
5	Git prints list to terminal	Output shows each worktree path and HEAD	/path/to/main-worktree 123abc [main] /path/to/feature-worktree 456def [feature-branch]
6	Command ends	All worktrees listed	Done

💡 All linked worktrees have been listed with their paths and HEAD states.

Status Tracker

Variable	Start	After Step 2	After Step 3	Final
worktrees_list	empty	paths of all worktrees found	paths + HEAD info for each worktree	complete list with paths and HEAD info

Key Moments - 2 Insights

Why does the output show commit hashes and branch names?

Because git reads the HEAD of each worktree to show what commit or branch it currently points to, as seen in execution_table step 3 and 5.

What if I have no extra worktrees created?

The list will show only the main worktree path and its HEAD info, or just one entry, as git always includes the main worktree.

Visual Quiz - 3 Questions

Look at the execution_table step 5 output, what does '[feature-branch]' represent?

A The current branch checked out in that worktree

B The remote repository URL

C The last commit message

D The worktree creation date

💡 Hint

Refer to execution_table step 3 and 5 where HEAD info is read and displayed.

At which step does git gather the commit hashes for each worktree?

A Step 1

B Step 3

C Step 2

D Step 5

💡 Hint

Check execution_table where HEAD info is read for each worktree.

If you create a new worktree, how will the variable 'worktrees_list' change after step 2?

A It will include commit hashes

B It will remain empty

C It will include the new worktree path

D It will be deleted

💡 Hint

See variable_tracker after step 2 where paths of all worktrees are found.

Concept Snapshot

git worktree list
- Lists all worktrees linked to the repo
- Shows path and current HEAD (branch or commit)
- Reads .git/worktrees directory
- Useful to see multiple working copies
- Output includes main and extra worktrees

Full Transcript

The 'git worktree list' command shows all worktrees connected to your git repository. When you run it, git reads the .git/worktrees directory to find all linked worktrees. Then it reads the HEAD information for each worktree to find out which branch or commit is currently checked out. Finally, it prints a list showing each worktree's path and its HEAD state. This helps you see all your working copies and their current branches or commits at a glance.