Git prune Quiz

Check your understanding of unreachable-object pruning, dry runs, expiration, reachability protection, and maintenance boundaries.

9 questions

Knowledge check

Check your understanding of unreachable-object pruning, dry runs, expiration, reachability protection, and maintenance boundaries.

You can retake this quiz whenever you like.

0:00

0/0

What does `git prune` primarily remove?

`git prune` removes eligible unreachable objects from the object database.
What is the safest first form for seeing what prune would remove?

`-n` performs a dry run and `-v` lists the candidates.
What does `--expire=now` mean for an eligible unreachable object?

`--expire=now` removes the age delay for otherwise eligible unreachable objects.
Why can a deleted branch's commits remain recoverable before pruning?

Reflogs and related retention can keep objects available even after they stop being reachable from current refs.
What does an additional `<head>` argument do to pruning reachability?

Additional heads contribute to the set of objects considered reachable.
Which command is the normal high-level maintenance interface?

The official prune documentation recommends `git gc` for most routine repository maintenance.
Which pairing is correct?

`git fsck` checks object validity/connectivity, while `git prune` performs destructive removal of eligible unreachable objects.
What does `--progress` request?

`--progress` requests progress reporting during pruning.
What happens to unreachable objects that are already packed?

The official `git-prune` documentation says unreachable packed objects remain and points to `git repack` when that is not desired.

What does `git prune` primarily remove?