Submodule status and sync in Git - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Check submodule status output

You run the command git submodule status in a repository with one submodule. What does the output show if the submodule is checked out at the commit recorded in the main repo?

Git

git submodule status

A a1b2c3d4e5f6g7h8i9j0klmnopqrstuv submodule_path (heads/main)

B +a1b2c3d4e5f6g7h8i9j0klmnopqrstuv submodule_path

C a1b2c3d4e5f6g7h8i9j0klmnopqrstuv submodule_path

D -a1b2c3d4e5f6g7h8i9j0klmnopqrstuv submodule_path

💡 Hint

Look for the symbol at the start of the line indicating submodule sync state.

The output line starts with a space if the submodule is exactly at the commit recorded in the main repo. A '-' means the submodule is not initialized, '+' means the submodule is ahead or behind, and a space means clean.

💻 Command Output

intermediate

Effect of git submodule sync

What is the effect of running git submodule sync in a repository with submodules?

Git

git submodule sync

A Removes all submodules from the repository

B Fetches the latest commits for all submodules

C Initializes and clones missing submodules

D Updates the URLs of submodules in .git/config to match .gitmodules

💡 Hint

Think about syncing configuration rather than fetching code.

git submodule sync updates the local configuration URLs for submodules to match the URLs defined in the .gitmodules file. It does not fetch or clone code.

🔀 Workflow

advanced

Correct sequence to update submodules after URL change

You changed the URL of a submodule in .gitmodules. What is the correct sequence of commands to update your local config and fetch the submodule code?

A 1,2,4,3

B 3,1,2,4

C 1,3,2,4

D 2,1,3,4

💡 Hint

Sync URLs first, then update submodules, then check status.

First, git submodule sync updates URLs. Then git submodule update --init --recursive fetches and checks out submodules. Checking status last confirms the state. Fetching all remotes is not required here.

❓ Troubleshoot

advanced

Error when submodule commit is missing locally

You run git submodule update but get an error that the commit is not found. What is the most likely cause?

A The submodule is already up to date

B The submodule repository URL is incorrect or unreachable

C The main repository has no submodules configured

D The main repository's HEAD is detached

💡 Hint

Think about why the commit might not be available locally.

If the submodule URL is wrong or unreachable, Git cannot fetch the commit, causing this error.

✅ Best Practice

expert

Best practice to keep submodules in sync across team

Which practice best ensures all team members have the correct submodule commits and URLs after a change?

A Update .gitmodules, commit, push, then instruct team to run <code>git submodule sync</code> and <code>git submodule update --init --recursive</code>

B Commit changes to .gitmodules and run <code>git submodule sync</code> locally only

C Ignore .gitmodules and manually clone submodules

D Delete and re-add submodules on each machine

💡 Hint

Think about sharing configuration and commands for team consistency.

Updating and committing .gitmodules shares URL changes. Team members then sync config and update submodules to get correct commits.