Shallow clones with depth in Git - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of shallow clone with depth 1

What is the output of the following command when cloning a large repository with many commits?

git clone --depth 1 https://github.com/example/repo.git

Choose the most accurate description of the clone result.

Git

git clone --depth 1 https://github.com/example/repo.git

A The repository is cloned with only the latest commit and no earlier history.

B The repository clone fails because depth must be greater than 1.

C The repository is cloned with the full commit history but no tags.

D The repository is cloned with all branches but only the last 10 commits each.

💡 Hint

Think about what the --depth option limits in a git clone.

Using --depth 1 creates a shallow clone with only the latest commit, reducing download size and time.

🧠 Conceptual

intermediate

Effect of shallow clone on git log

After cloning a repository with git clone --depth 3, what will git log show compared to a full clone?

A The log will show commits from all branches, but only 3 per branch.

B All commits will be shown but with limited details.

C Only the last 3 commits will be shown in the log.

D No commits will be shown until the full history is fetched.

💡 Hint

Consider what shallow cloning limits in the commit history.

A shallow clone with depth 3 contains only the latest 3 commits, so git log shows only those.

🔀 Workflow

advanced

Extending a shallow clone depth

You cloned a repository with git clone --depth 1. Later, you want to fetch more history to depth 5. Which command correctly extends the shallow clone to include the last 5 commits?

A git fetch --unshallow --depth=5

B git pull --depth 5

C git clone --depth 5

D git fetch --depth=5

💡 Hint

Think about how to fetch more commits after cloning shallowly.

Using git fetch --depth=5 extends the shallow clone to include the last 5 commits.

❓ Troubleshoot

advanced

Error when pushing from a shallow clone

You cloned a repository with git clone --depth 1 and made commits locally. When you try to push, you get an error:

error: refusing to push because the remote contains work that you do not have locally

What is the most likely cause?

A The shallow clone lacks full history, so git cannot verify the push is safe.

B You forgot to add files before committing.

C The remote repository is read-only.

D Your local branch is not tracking any remote branch.

💡 Hint

Consider how shallow clones affect push operations.

Shallow clones have incomplete history, so git refuses to push to avoid overwriting unknown commits.

✅ Best Practice

expert

Choosing shallow clone depth for CI pipelines

In a continuous integration (CI) pipeline, you want to speed up builds by cloning only necessary commits. Which depth value is best practice to balance speed and build correctness?

A Use full clone without depth to avoid any issues with missing history.

B Use depth 50 to include enough history for most build tools and tests.

C Use depth 1 to clone only the latest commit for fastest builds.

D Use depth 0 to clone no commits and fetch them later as needed.

💡 Hint

Think about the tradeoff between speed and completeness in CI.

Depth 50 often provides enough history for build tools while keeping clone time reasonable.