Bird
Raised Fist0
Gitdevops~10 mins

Cloning with submodules in Git - Interactive Code Practice

Choose your learning style10 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the command to clone a repository including its submodules.

Git
git clone --[1] <repository-url>
Drag options to blanks, or click blank then click option'
Arecursive
Bsubmodules
Cmodules
Drecurse-submodules
Attempts:
3 left
💡 Hint
Common Mistakes
Forgetting to include any submodule option
Using --modules which is not a valid option
2fill in blank
medium

Complete the command to initialize submodules after cloning without --recurse-submodules.

Git
git submodule [1]
Drag options to blanks, or click blank then click option'
Aupdate
Bclone
Cinit
Dfetch
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'update' instead of 'init' first
Trying to clone submodules directly
Using 'fetch' instead of 'init'
3fill in blank
hard

Fix the error in the command to update submodules recursively.

Git
git submodule update --[1]
Drag options to blanks, or click blank then click option'
Arecursive
Brecurse-submodules
Cinit
Dfetch
Attempts:
3 left
💡 Hint
Common Mistakes
Using --init which initializes but does not update
Using --fetch which is not a valid flag for update
4fill in blank
hard

Fill both blanks to clone a repository and initialize submodules manually.

Git
git clone <repo-url> && git submodule [1] && git submodule [2]
Drag options to blanks, or click blank then click option'
Ainit
Bupdate
Cfetch
Dstatus
Attempts:
3 left
💡 Hint
Common Mistakes
Reversing the order of init and update
Using fetch instead of update
Skipping init command
5fill in blank
hard

Fill all three blanks to clone a repo, initialize, and update submodules recursively.

Git
git clone --[1] <repo-url> && git submodule [2] && git submodule update --[3]
Drag options to blanks, or click blank then click option'
Arecurse-submodules
Binit
Crecursive
Dfetch
Attempts:
3 left
💡 Hint
Common Mistakes
Skipping init before update

Practice

(1/5)
1. What does the command git clone --recurse-submodules <repo_url> do?
easy
A. Clones the main repository and all its submodules in one step
B. Clones only the main repository without any submodules
C. Updates submodules after cloning the main repository
D. Removes submodules from the cloned repository

Solution

  1. Step 1: Understand the purpose of --recurse-submodules

    The option tells Git to clone the main repo and all submodules recursively in one command.
  2. Step 2: Compare with cloning without this option

    Without it, only the main repo is cloned; submodules need separate commands to fetch.
  3. Final Answer:

    Clones the main repository and all its submodules in one step -> Option A
  4. Quick Check:

    --recurse-submodules = clone main + submodules [OK]
Hint: Use --recurse-submodules to clone all at once [OK]
Common Mistakes:
  • Thinking it clones only the main repo
  • Confusing update with clone
  • Assuming it removes submodules
2. Which of the following is the correct command to clone a repository along with its submodules?
easy
A. git clone --update-submodules https://example.com/repo.git
B. git clone --init-submodules https://example.com/repo.git
C. git clone --recurse-submodules https://example.com/repo.git
D. git clone --submodule-update https://example.com/repo.git

Solution

  1. Step 1: Identify the correct flag for cloning with submodules

    The correct flag is --recurse-submodules to clone main repo and submodules together.
  2. Step 2: Check other options for validity

    Options --init-submodules, --update-submodules, and --submodule-update are not valid git clone flags.
  3. Final Answer:

    git clone --recurse-submodules https://example.com/repo.git -> Option C
  4. Quick Check:

    --recurse-submodules is the correct clone flag [OK]
Hint: Remember: clone with --recurse-submodules for submodules [OK]
Common Mistakes:
  • Using non-existent flags like --init-submodules
  • Mixing update commands with clone
  • Misspelling the flag
3. After cloning a repository without --recurse-submodules, you run git submodule update --init --recursive. What is the expected result?
medium
A. Submodules are initialized and updated to the correct commit
B. The main repository is recloned
C. Submodules are deleted from the repository
D. Nothing happens because submodules are not cloned

Solution

  1. Step 1: Understand the command purpose

    The command initializes submodules and updates them recursively to the commit recorded in the main repo.
  2. Step 2: Clarify what happens after cloning without submodules

    Submodules are present as empty folders; this command fetches their content properly.
  3. Final Answer:

    Submodules are initialized and updated to the correct commit -> Option A
  4. Quick Check:

    git submodule update --init --recursive = fetch submodules [OK]
Hint: Use update --init --recursive to fetch missing submodules [OK]
Common Mistakes:
  • Thinking it reclones the main repo
  • Assuming submodules get deleted
  • Believing nothing happens without --recurse-submodules
4. You cloned a repository with submodules but forgot to use --recurse-submodules. Running git submodule update --init gives an error. What is the most likely cause?
medium
A. The main repository was cloned with --recurse-submodules
B. The submodule URLs are missing or incorrect in .gitmodules
C. You need to delete the main repository and reclone
D. Submodules cannot be initialized after cloning

Solution

  1. Step 1: Analyze the error cause

    If submodule URLs in .gitmodules are missing or wrong, update --init fails to fetch them.
  2. Step 2: Check other options for correctness

    The main repository was cloned with --recurse-submodules is false because main repo was cloned without --recurse-submodules; C and D are incorrect as recloning or inability to init is not required.
  3. Final Answer:

    The submodule URLs are missing or incorrect in .gitmodules -> Option B
  4. Quick Check:

    Missing or wrong URLs cause submodule init errors [OK]
Hint: Check .gitmodules URLs if submodule update fails [OK]
Common Mistakes:
  • Assuming recloning is always needed
  • Thinking submodules can't be initialized later
  • Ignoring .gitmodules configuration
5. You cloned a repository with nested submodules but only ran git submodule update --init. What is the best command to ensure all nested submodules are also initialized and updated?
hard
A. git submodule update --recursive
B. git submodule init --recursive
C. git clone --recurse-submodules
D. git submodule update --init --recursive

Solution

  1. Step 1: Understand nested submodules

    Nested submodules require recursive initialization and update to fetch all levels.
  2. Step 2: Identify the correct command

    The command with both --init and --recursive flags initializes and updates all nested submodules properly.
  3. Step 3: Check other options

    git submodule update --recursive misses --init, C is for cloning not updating, D is invalid syntax.
  4. Final Answer:

    git submodule update --init --recursive -> Option D
  5. Quick Check:

    Use --init --recursive to update nested submodules [OK]
Hint: Add --init --recursive to update all nested submodules [OK]
Common Mistakes:
  • Forgetting --init when updating submodules
  • Using clone commands after cloning
  • Using invalid flags like --recursive with init only
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard