The .git directory structure - Step-by-Step Execution

Process Flow - The .git directory structure

Initialize Git Repo

↓

.git directory created

↓

Create subdirectories: objects, refs, info

↓

Create files: HEAD, config, description

↓

Store commits, branches, tags inside .git

↓

Git commands read/write .git contents

This flow shows how the .git directory is created and structured when you initialize a Git repository, and how Git uses it to store all version control data.

Execution Sample

Git

git init
ls -la .git
cat .git/HEAD

Initialize a Git repo, list .git directory contents, and show the HEAD file content.

Process Table

Step	Command	Action	Result
1	git init	Create .git directory and initial files	.git directory with subfolders and files created
2	ls -la .git	List contents of .git directory	Shows folders: objects, refs, info and files: HEAD, config, description
3	cat .git/HEAD	Read HEAD file content	ref: refs/heads/main
4	git status	Git reads .git to show repo status	Shows working tree clean, branch main

💡 Initialization complete, .git directory fully set up and ready for version control

Status Tracker

Variable	Start	After git init	After git status
.git directory	none	created with subfolders and files	unchanged
HEAD file	none	contains 'ref: refs/heads/main'	unchanged
refs/heads/main	none	not yet created (no commits)	unchanged

Key Moments - 3 Insights

Why does the .git directory have subfolders like objects and refs?

Because Git organizes data inside .git: 'objects' store all content snapshots, 'refs' store pointers to branches and tags. See execution_table step 1 and 2.

What does the HEAD file inside .git represent?

HEAD points to the current branch reference, usually 'refs/heads/main' initially. This is shown in execution_table step 3.

Why does git status read the .git directory?

Git reads .git to know the current branch and commit state to show status. This is shown in execution_table step 4.

Visual Quiz - 3 Questions

Look at the execution table, what does the command 'cat .git/HEAD' output?

A ref: refs/heads/main

B List of files in .git

C Current commit hash

D Error: file not found

💡 Hint

Check execution_table row 3 for the output of 'cat .git/HEAD'

At which step is the .git directory created?

A Step 2

B Step 3

C Step 1

D Step 4

💡 Hint

Look at execution_table step 1 where 'git init' creates the .git directory

If you run 'git status' before 'git init', what would happen?

A Git creates .git directory automatically

B Git errors because .git directory is missing

C Git shows working tree clean

D Git shows current branch as main

💡 Hint

Refer to variable_tracker showing .git directory is created only after 'git init'

Concept Snapshot

The .git directory is created by 'git init' and stores all Git data.
It contains subfolders like 'objects' (data storage), 'refs' (branches/tags), and files like 'HEAD' (current branch pointer).
Git commands read/write inside .git to track versions.
Understanding .git helps you know how Git manages your project history.

Full Transcript

When you run 'git init', Git creates a hidden folder called .git in your project. This folder holds everything Git needs to track your project versions. Inside .git, there are folders like 'objects' where Git stores snapshots of your files, and 'refs' where it keeps pointers to branches and tags. The HEAD file inside .git points to the current branch you are working on, usually 'refs/heads/main' at first. When you run commands like 'git status', Git reads the .git folder to understand your project's current state. Without the .git directory, Git cannot track changes or versions. This structure is the heart of Git's version control system.