Removing submodules in Git - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output after removing a submodule directory?

You run these commands in a git repository:

git rm --cached path/to/submodule
rm -rf path/to/submodule
git commit -m "Remove submodule"

What will git status show immediately after the commit?

A No changes, clean working tree

B Deleted submodule directory shown as deleted

C Submodule still listed in .gitmodules as modified

D Untracked files in submodule directory

💡 Hint

Think about what happens when you remove a submodule properly and commit.

After removing the submodule with git rm --cached and deleting its directory, committing removes it from the index and working tree. So git status shows a clean state with no changes.

❓ Configuration

intermediate

Which file must be edited to fully remove a submodule?

You want to completely remove a submodule from your git project. Besides removing the submodule directory and running git rm --cached, which file must you edit to remove the submodule reference?

A .gitattributes

B .gitmodules

C .gitignore

D config

💡 Hint

This file tracks submodule paths and URLs.

The .gitmodules file contains the configuration for submodules. Removing the submodule requires deleting its entry from this file.

❓ Troubleshoot

advanced

Why does git still show a submodule after removal?

You removed a submodule directory and ran git rm --cached and committed. But git status still shows the submodule as modified. What is the most likely cause?

A You did not run git submodule update

B You forgot to delete the submodule directory

C The submodule entry remains in .gitmodules and .git/config

D The submodule repository is corrupted

💡 Hint

Check all places where submodule info is stored.

Even after removing the submodule directory and index entry, if .gitmodules or .git/config still reference the submodule, git will show it as modified.

🔀 Workflow

advanced

Correct sequence to fully remove a git submodule

Arrange the steps in the correct order to fully remove a git submodule named libs/foo:

A 2,3,1,4

B 1,2,3,4

C 1,3,2,4

D 2,1,3,4

💡 Hint

Think about removing from index before deleting files and updating config.

First remove from index with git rm --cached, then remove from .gitmodules, delete directory, then commit.

✅ Best Practice

expert

What is the safest way to remove a submodule to avoid repository corruption?

Which practice helps avoid repository corruption when removing a git submodule?

A Run git rm --cached, remove submodule entry from .gitmodules, delete directory, then commit

B Remove submodule directory manually, then run git rm --cached

C Delete submodule directory and commit directly without git rm

D Only edit .gitmodules and commit, leaving directory intact

💡 Hint

Follow git's recommended removal steps carefully.

The safest way is to remove the submodule from the index first, then remove config entries, delete directory, and commit. This prevents leftover references causing corruption.

Practice

1. What is the first step to remove a Git submodule from your project?

easy

A. Commit the changes immediately

B. Delete the submodule folder manually

C. Unregister the submodule using git submodule deinit

D. Run git rm --cached on the main repository

Solution

1. Step 1: Unregister the submodule

   Use git submodule deinit <path> to unregister the submodule from Git's configuration.

2. Step 2: Remove submodule files and commit

   After unregistering, delete the submodule folder and commit the changes to keep the project clean.

3. Final Answer:

   Unregister the submodule using git submodule deinit -> Option C

4. Quick Check:

   First step is unregistering submodule [OK]

Hint: Always unregister submodule before deleting files [OK]

Common Mistakes:

• Deleting folder before unregistering causes errors
• Committing before unregistering submodule
• Skipping unregister step

2. Which command correctly removes a submodule's cached entry from Git's index?

easy

A. git rm <submodule_path>

B. git delete submodule <submodule_path>

C. git submodule remove <submodule_path>

D. git rm --cached <submodule_path>

Solution

1. Step 1: Remove cached submodule entry

   Use git rm --cached <submodule_path> to remove the submodule from Git's index without deleting files immediately.

2. Step 2: Delete submodule folder and commit

   After removing cached entry, delete the folder manually and commit the changes.

3. Final Answer:

   git rm --cached <submodule_path> -> Option D

4. Quick Check:

   Remove cached entry with git rm --cached [OK]

Hint: Use --cached to remove from index but keep files temporarily [OK]

Common Mistakes:

• Using git rm without --cached deletes files immediately
• Using non-existent git submodule remove command
• Trying git delete submodule which is invalid

3. Given these commands run in order, what is the final state of the submodule folder?

git submodule deinit mysub
rm -rf .git/modules/mysub
git rm --cached mysub
rm -rf mysub
git commit -m "Remove submodule"

medium

A. The submodule folder and Git data are fully removed

B. The submodule folder remains but is untracked

C. Only Git data is removed, folder remains

D. Submodule is still registered and tracked

Solution

1. Step 1: Unregister and remove Git data

   git submodule deinit mysub unregisters the submodule, and rm -rf .git/modules/mysub deletes its Git data.

2. Step 2: Remove cached index and folder, then commit

   git rm --cached mysub removes it from Git index, rm -rf mysub deletes the folder, and commit saves changes.

3. Final Answer:

   The submodule folder and Git data are fully removed -> Option A

4. Quick Check:

   All steps done means full removal [OK]

Hint: Deinit, remove Git data, rm cached, delete folder, commit [OK]

Common Mistakes:

• Forgetting to delete .git/modules data
• Not committing after removal
• Deleting folder before unregistering

4. You ran rm -rf mysub before git submodule deinit mysub. What problem might occur?

medium

A. Git still tracks the submodule and shows errors on next fetch

B. The submodule folder is restored automatically

C. Git removes the submodule automatically without errors

D. No problem, this is the correct order

Solution

1. Step 1: Understand order importance

   Deleting the folder before unregistering leaves Git still tracking the submodule path.

2. Step 2: Resulting error state

   Git will show errors or warnings because the submodule is missing but still registered.

3. Final Answer:

   Git still tracks the submodule and shows errors on next fetch -> Option A

4. Quick Check:

   Delete folder before deinit causes tracking errors [OK]

Hint: Always deinit before deleting submodule folder [OK]

Common Mistakes:

• Deleting folder first then deinit
• Ignoring Git errors after removal
• Assuming folder deletion unregisters submodule

5. You want to completely remove a submodule named libs/toolkit from your project. Which sequence of commands correctly removes it and cleans all related data?

hard

A. git rm libs/toolkit; rm -rf libs/toolkit; git commit -m "Remove submodule"

B. git submodule deinit libs/toolkit; rm -rf .git/modules/libs/toolkit; git rm --cached libs/toolkit; rm -rf libs/toolkit; git commit -m "Remove submodule"

C. rm -rf libs/toolkit; git submodule deinit libs/toolkit; git commit -m "Remove submodule"

D. git submodule remove libs/toolkit; git commit -m "Remove submodule"

Solution

1. Step 1: Unregister and remove Git submodule data

   Run git submodule deinit libs/toolkit to unregister, then delete Git metadata with rm -rf .git/modules/libs/toolkit.

2. Step 2: Remove cached index and folder, then commit

   Use git rm --cached libs/toolkit to remove from index, delete the folder manually, and commit changes.

3. Final Answer:

   git submodule deinit libs/toolkit; rm -rf .git/modules/libs/toolkit; git rm --cached libs/toolkit; rm -rf libs/toolkit; git commit -m "Remove submodule" -> Option B

4. Quick Check:

   Full removal requires unregister, delete Git data, rm cached, delete folder, commit [OK]

Hint: Deinit, delete .git/modules, rm cached, delete folder, commit [OK]

Common Mistakes:

• Skipping removal of .git/modules data
• Using non-existent git submodule remove command
• Deleting folder before unregistering