Why submodules manage nested repos in Git - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use Git submodules for nested repositories?

Which of the following best explains why Git submodules are used to manage nested repositories?

A They allow a repository to include and track a specific commit of another repository as a subdirectory.

B They automatically merge changes from nested repositories into the main repository without manual intervention.

C They convert nested repositories into branches within the main repository for easier management.

D They duplicate the entire nested repository content inside the main repository to avoid external dependencies.

💡 Hint

Think about how Git keeps track of external projects inside a main project.

Git submodules let you include another repository inside your repository as a folder, tracking a specific commit. This keeps the nested repo separate but linked.

💻 Command Output

intermediate

Output of git submodule status command

What is the output of the command git submodule status immediately after cloning a repository with submodules but before initializing them?

Git

git clone https://example.com/project.git
cd project
git submodule status

A 3f4e2a1c7d8b9f0a1234567890abcdef12345678 path/to/submodule (heads/main)

B +3f4e2a1c7d8b9f0a1234567890abcdef12345678 path/to/submodule (detached)

C No submodules found.

D -3f4e2a1c7d8b9f0a1234567890abcdef12345678 path/to/submodule (new commits)

💡 Hint

Check the symbol before the commit hash indicating submodule state.

The '-' symbol means the submodule is not initialized yet. The commit hash and path show the expected commit and location.

🔀 Workflow

advanced

Correct workflow to update a submodule to latest commit

Which sequence of commands correctly updates a Git submodule to the latest commit on its default branch and commits this change in the main repository?

A

git submodule update --remote
 git add path/to/submodule
 git commit -m "Update submodule"

B

git submodule sync
 git push
 git commit -m "Update submodule"

C

git clone submodule_url path/to/submodule
 git commit -m "Update submodule"

D

git pull
 git submodule init
 git commit -m "Update submodule"

💡 Hint

Think about how to fetch latest changes and record them in the main repo.

Using git submodule update --remote fetches the latest commit from the submodule's remote branch. Then you stage and commit the updated submodule reference in the main repo.

❓ Troubleshoot

advanced

Resolving detached HEAD state in submodule

You notice your Git submodule is in a detached HEAD state after updating. Which command fixes this by checking out the submodule's default branch?

A git submodule sync

B git reset --hard HEAD

C cd path/to/submodule && git checkout main

D git submodule update --remote --merge

💡 Hint

Detached HEAD means you are not on a branch inside the submodule.

Changing directory into the submodule and checking out the main branch moves from detached HEAD to a branch.

✅ Best Practice

expert

Best practice for committing changes in submodules

When you make changes inside a Git submodule, what is the best practice to ensure the main repository tracks these changes correctly?

A Commit changes only in the main repository; submodule commits are tracked automatically.

B Commit changes inside the submodule, then commit the updated submodule reference in the main repository.

C Make changes and commit only in the submodule; no need to update the main repository.

D Delete and re-add the submodule after changes to refresh the main repository tracking.

💡 Hint

Think about how Git tracks submodule versions inside the main repo.

Changes inside a submodule must be committed there first. Then the main repo must commit the updated submodule pointer to track the new commit.