0
0
Gitdevops~10 mins

git fsck for repository integrity - Interactive Code Practice

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

Complete the command to check the integrity of a Git repository.

Git
git [1]
Drag options to blanks, or click blank then click option'
Afsck
Bcommit
Cclone
Dstatus
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'git status' instead of 'git fsck'.
Trying 'git commit' which is for saving changes.
2fill in blank
medium

Complete the command to check the repository and show corrupted objects.

Git
git fsck --[1]
Drag options to blanks, or click blank then click option'
Aquiet
Blost-found
Cfull
Ddangling
Attempts:
3 left
💡 Hint
Common Mistakes
Using '--quiet' which suppresses output.
Using '--dangling' which only shows dangling objects.
3fill in blank
hard

Fix the error in the command to check repository integrity with verbose output.

Git
git fsck --[1]
Drag options to blanks, or click blank then click option'
Acheck
Bquiet
Cfull
Dverbose
Attempts:
3 left
💡 Hint
Common Mistakes
Using '--check' which is not a valid option.
Using '--quiet' which reduces output.
4fill in blank
hard

Fill both blanks to find dangling objects and show them in the lost and found.

Git
git fsck --[1] --[2]
Drag options to blanks, or click blank then click option'
Adangling
Bquiet
Clost-found
Dfull
Attempts:
3 left
💡 Hint
Common Mistakes
Mixing up 'quiet' with 'dangling'.
Using 'full' instead of 'lost-found'.
5fill in blank
hard

Fill all three blanks to check the repository, show verbose output, and save dangling objects.

Git
git fsck --[1] --[2] --[3]
Drag options to blanks, or click blank then click option'
Afull
Bverbose
Clost-found
Dquiet
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'quiet' instead of 'full'.
Forgetting to include 'lost-found' to save dangling objects.