The .git directory structure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to show the main directory that stores all Git data.

Git

ls -a | grep [1]

Drag options to blanks, or click blank then click option'

Asrc

Bdocs

C.git

Dbin

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a regular folder like 'src' or 'bin' instead of the hidden '.git' directory.

The .git directory is the hidden folder where Git stores all its data and history.

2fill in blank

medium

Complete the command to list the contents inside the .git directory.

Git

ls [1]/.git

Drag options to blanks, or click blank then click option'

A/var/log

B/home/user/project

C..

D.

Attempts:

3 left

💡 Hint

Common Mistakes

Using an absolute path that may not exist or is unrelated.

Using '..' which points to the parent directory.

The dot . means the current directory, so ls ./.git lists the contents of the .git folder inside the current directory.

3fill in blank

hard

Fix the error in the command to show the HEAD file inside the .git directory.

Git

cat [1]/HEAD

Drag options to blanks, or click blank then click option'

A.git

Bgit

Chead

DHEAD

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'git' without the dot, which is not the correct directory.

Using 'HEAD' as a directory instead of a file.

The HEAD file is inside the .git directory. The command must use the correct folder name .git (with a dot) to access it.

4fill in blank

hard

Fill both blanks to create a command that shows the contents of the config file inside the .git directory.

Git

cat [1]/[2]

Drag options to blanks, or click blank then click option'

A.git

Bconfig

CHEAD

Drefs

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'HEAD' or 'refs' instead of 'config' for the file name.

Omitting the dot in '.git'.

The config file inside the .git directory holds repository settings. The command cat .git/config displays its contents.

5fill in blank

hard

Fill all three blanks to create a command that lists files inside the info subdirectory of the objects directory within .git.

Git

ls [1]/[2]/[3]

Drag options to blanks, or click blank then click option'

A.git

Bobjects

Cinfo

Drefs

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'refs' instead of 'info' as the last directory.

Omitting the dot in '.git'.

The objects directory inside .git stores all Git objects. The info subdirectory contains additional info files. The command ls .git/objects/info lists those files.

Practice

1. What is the main purpose of the .git directory in a Git project?

easy

A. It stores all the data and history of the Git repository.

B. It contains the source code files of the project.

C. It holds temporary files created by the operating system.

D. It stores user configuration settings unrelated to Git.

Solution

1. Step 1: Understand the role of .git directory

   The .git directory is created when you initialize a Git repository and it stores all Git-related data.

2. Step 2: Differentiate from other directories

   Source code files are outside .git, and temporary or unrelated user files are not stored here.

3. Final Answer:

   It stores all the data and history of the Git repository. -> Option A

4. Quick Check:

   .git = Git data storage [OK]

Hint: Remember: .git holds Git's data, not project files [OK]

Common Mistakes:

• Confusing .git with project source files
• Thinking it stores temporary OS files
• Assuming it holds unrelated user configs

2. Which of the following is a correct folder inside the .git directory?

easy

A. src

B. temp

C. bin

D. objects

Solution

1. Step 1: Recall standard .git folders

   The .git directory contains folders like objects, refs, and hooks.

2. Step 2: Identify the correct folder

   Among the options, only objects is a valid folder inside .git.

3. Final Answer:

   objects -> Option D

4. Quick Check:

   objects folder exists in .git [OK]

Hint: Look for Git-specific folders like objects [OK]

Common Mistakes:

• Choosing project folders like src
• Selecting unrelated folders like bin or temp

3. If you look inside the .git/refs/heads folder, what will you typically find?

medium

A. Configuration settings for Git hooks

B. Binary objects of the project files

C. Files representing branches in the repository

D. Temporary files created during commits

Solution

1. Step 1: Understand refs/heads purpose

   The refs/heads folder stores files named after branches, each containing the commit hash of the branch tip.

2. Step 2: Differentiate from other folders

   Binary objects are in objects, hooks configs are in hooks, and temporary files are not stored here.

3. Final Answer:

   Files representing branches in the repository -> Option C

4. Quick Check:

   refs/heads = branch pointers [OK]

Hint: Remember: refs/heads holds branch names [OK]

Common Mistakes:

• Confusing branch refs with object storage
• Thinking hooks configs are here
• Assuming temporary files are stored here

4. You accidentally deleted the .git/HEAD file. What problem will this cause?

medium

A. Your project files will be deleted.

B. Git will lose track of the current branch or commit.

C. Git will stop tracking remote repositories.

D. Nothing will happen; Git recreates it automatically.

Solution

1. Step 1: Understand the role of HEAD file

   The HEAD file points to the current branch or commit checked out in the working directory.

2. Step 2: Consequence of deleting HEAD

   Without HEAD, Git cannot know which branch or commit is active, causing errors in commands.

3. Final Answer:

   Git will lose track of the current branch or commit. -> Option B

4. Quick Check:

   HEAD tracks current branch [OK]

Hint: HEAD file = current branch pointer; deleting it breaks Git [OK]

Common Mistakes:

• Thinking project files get deleted
• Assuming remote tracking is affected
• Believing Git auto-recreates HEAD always

5. You want to manually inspect the commit history by reading files inside the .git directory. Which folder should you explore to find the actual commit objects?

hard

A. objects

B. hooks

C. refs

D. logs

Solution

1. Step 1: Identify where commit data is stored

   The objects folder stores all Git objects including commits, trees, and blobs in compressed form.

2. Step 2: Differentiate from other folders

   refs holds pointers to commits, hooks contains scripts, and logs track changes to refs.

3. Final Answer:

   objects -> Option A

4. Quick Check:

   Commit data = objects folder [OK]

Hint: Commit objects live in objects folder inside .git [OK]

Common Mistakes:

• Confusing refs with actual commit data
• Looking in hooks or logs for commits
• Assuming commit data is in project files