Question 1 of 7
What storage representation does `git pack-refs` manage?
`git pack-refs` packs refs into the packed-refs representation; it does not repack Git objects.
Quiz
Git pack-refs Quiz
Check your understanding of packed refs, selection patterns, pruning, and the boundary between ref storage and object storage.
7 questions
Knowledge check
Git pack-refs Quiz
Check your understanding of packed refs, selection patterns, pruning, and the boundary between ref storage and object storage.
- Skip a hard question and review it before your results.
- Questions and answer options can shuffle between attempts.
You can retake this quiz whenever you like.
0:00
Question 2 of 7
What does `git pack-refs --all` request?
`--all` requests packing of all refs that are eligible under the command's rules.
Question 3 of 7
What does `--no-prune` change?
`--no-prune` keeps the loose ref files after packing them.
Question 4 of 7
When both `--include` and `--exclude` match a ref, which selection takes precedence?
The official documentation states that exclusion takes precedence over inclusion.
Question 5 of 7
Why is `git pack-refs` different from `git repack`?
The two commands operate on different repository storage layers: refs versus Git objects.
Question 6 of 7
What should filesystem-oriented scripts avoid assuming?
A ref can be stored in packed-refs instead of as an individual loose file.
Question 7 of 7
What is the intended role of `git pack-refs --auto`?
`--auto` uses the repository's current ref-storage state to decide whether packing is warranted.
Quiz results
0/0
Review
-
What storage representation does `git pack-refs` manage?Hint used
-
What does `git pack-refs --all` request?Hint used
-
What does `--no-prune` change?Hint used
-
When both `--include` and `--exclude` match a ref, which selection takes precedence?Hint used
-
Why is `git pack-refs` different from `git repack`?Hint used
-
What should filesystem-oriented scripts avoid assuming?Hint used
-
What is the intended role of `git pack-refs --auto`?Hint used