Why submodules manage nested repos in Git - Visual Breakdown

Process Flow - Why submodules manage nested repos

Main Repo

↓

Add Submodule

↓

Submodule Repo Cloned

↓

Main Repo Tracks Submodule Commit

↓

Update Submodule Separately

↓

Commit Submodule Change in Main Repo

Shows how a main git repo adds and tracks a nested repo as a submodule, managing its commit separately.

Execution Sample

Git

git submodule add https://github.com/example/lib.git libs/lib
cd libs/lib
git checkout v1.0
cd ../..
git commit -am "Add lib submodule at v1.0"

Adds a nested repo as a submodule, checks out a version, then commits the submodule reference in the main repo.

Process Table

Step	Action	Result	Main Repo State	Submodule State
1	Run 'git submodule add https://github.com/example/lib.git libs/lib'	Submodule cloned into libs/lib	Tracks submodule path and commit	Cloned at HEAD of default branch
2	cd libs/lib	Enter submodule directory	No change	Inside submodule repo
3	git checkout v1.0	Submodule checked out at tag v1.0	No change	Detached HEAD at v1.0
4	cd ../..	Return to main repo root	No change	No change
5	git commit -am "Add lib submodule at v1.0"	Main repo records submodule commit	Submodule commit recorded in .gitmodules and index	No change
6	Later, update submodule	Submodule can be updated independently	Main repo must commit updated submodule commit	Submodule can move to new commit
7	Exit	Process complete	Main repo tracks specific submodule commit	Submodule is nested repo managed separately

💡 Submodule manages nested repo commit separately; main repo tracks submodule commit reference.

Status Tracker

Variable	Start	After Step 1	After Step 3	After Step 5	Final
Main Repo .gitmodules	empty	contains submodule path and URL	no change	tracked submodule commit	tracked submodule commit
Submodule Commit	none	cloned at HEAD	checked out v1.0 tag	no change	can update independently

Key Moments - 3 Insights

Why does the main repo track a specific commit of the submodule?

Because the main repo records the exact commit of the submodule it uses, ensuring consistent versions (see execution_table step 5).

Can you update the submodule independently from the main repo?

Yes, you can update the submodule repo separately, but you must commit the new submodule commit in the main repo to track the change (see execution_table step 6).

What happens if you don't commit the submodule update in the main repo?

The main repo will still point to the old submodule commit, causing version mismatch (see execution_table step 6 and exit_note).

Visual Quiz - 3 Questions

Look at the execution_table at step 3, what is the submodule state?

A Cloned at HEAD of default branch

B Detached HEAD at tag v1.0

C Submodule commit recorded in main repo

D No submodule present

💡 Hint

Check the 'Submodule State' column at step 3 in execution_table.

At which step does the main repo record the submodule commit?

A Step 1

B Step 3

C Step 5

D Step 6

💡 Hint

Look at the 'Main Repo State' column for when the commit happens in execution_table.

If you update the submodule but do not commit in the main repo, what happens?

A Main repo tracks old submodule commit causing mismatch

B Main repo tracks new submodule commit automatically

C Submodule is deleted

D Main repo breaks and cannot commit

💡 Hint

Refer to key_moments about committing submodule updates and execution_table step 6.

Concept Snapshot

Git submodules let you include a nested repo inside a main repo.
You add a submodule with 'git submodule add <url> <path>'.
The main repo tracks a specific commit of the submodule.
You update submodules separately and commit their new commit in main repo.
This keeps nested repos versions consistent and manageable.

Full Transcript

This visual execution shows how git submodules manage nested repositories. First, you add a submodule to your main repo, which clones the nested repo inside a folder. Then you can checkout a specific commit or tag in the submodule. The main repo tracks this exact commit in its .gitmodules and index. Later, you can update the submodule independently, but you must commit the new submodule commit in the main repo to keep versions consistent. If you don't commit the update, the main repo still points to the old submodule commit, causing mismatch. This process helps manage nested repos clearly and safely.