Shallow clones with depth in Git - Step-by-Step Execution

Process Flow - Shallow clones with depth

Start: git clone command

↓

Check for --depth option

↓

Clone limited

↓

history only

↓

Create local repo with limited commits

↓

End

The git clone process checks if a depth option is given. If yes, it clones only recent commits up to that depth, creating a shallow clone. Otherwise, it clones the full history.

Execution Sample

Git

git clone --depth 3 https://github.com/example/repo.git

This command clones only the last 3 commits from the remote repository, creating a shallow clone.

Process Table

Step	Action	Depth Option	Commits Cloned	Result
1	Start clone command	--depth 3	N/A	Prepare to clone repo
2	Check for depth option	--depth 3	N/A	Depth option found: 3
3	Fetch commits	--depth 3	3	Only last 3 commits fetched
4	Create local repo	--depth 3	3	Local repo created with shallow history
5	Clone complete	--depth 3	3	Shallow clone ready

💡 Clone stops after fetching 3 commits due to depth limit

Status Tracker

Variable	Start	After Step 2	After Step 3	Final
depth	undefined	3	3	3
commits_fetched	0	0	3	3
local_repo_state	empty	empty	partial history	partial history

Key Moments - 3 Insights

Why does the clone only have 3 commits instead of the full history?

Because the --depth 3 option limits the clone to the last 3 commits, as shown in execution_table step 3 where only 3 commits are fetched.

Can you push changes from a shallow clone?

Yes, but some operations may be limited because the history is incomplete. The shallow clone has only recent commits (execution_table step 4), so pushing might require fetching more history first.

What happens if you omit the --depth option?

The clone fetches the full commit history (execution_table step 2 'No' branch), resulting in a complete local repository.

Visual Quiz - 3 Questions

Look at the execution_table at step 3, how many commits are fetched?

A 0 commits

B All commits

C 3 commits

D 1 commit

💡 Hint

Refer to the 'Commits Cloned' column at step 3 in the execution_table.

At which step does git confirm the depth option is used?

A Step 2

B Step 1

C Step 4

D Step 5

💡 Hint

Check the 'Action' and 'Depth Option' columns in execution_table step 2.

If the --depth option was removed, how would the 'Commits Cloned' column change?

A It would show 3 commits

B It would show all commits

C It would show 0 commits

D It would show 1 commit

💡 Hint

Without depth, git clones full history as explained in key_moments and concept_flow.

Concept Snapshot

git clone --depth <n> <repo_url>
- Clones only the last n commits
- Creates a shallow clone with limited history
- Faster and smaller download
- Some git operations may be limited
- Omit --depth for full clone

Full Transcript

When you run git clone with the --depth option, git checks this option and fetches only the last specified number of commits from the remote repository. This creates a shallow clone with limited history, which is faster and uses less space. The execution table shows step-by-step how git processes the command: starting the clone, detecting the depth option, fetching only the last 3 commits, creating the local repository with partial history, and completing the clone. Variables like depth and commits_fetched track these changes. Beginners often wonder why the history is limited or if they can push changes; the key moments clarify these points. The visual quiz tests understanding of commit counts and steps where depth is recognized. Remember, omitting --depth clones the full history.