Repository (committed history) in Git - Step-by-Step Execution

Process Flow - Repository (committed history)

Create Repository

↓

Make Changes to Files

↓

Stage Changes (git add)

↓

Commit Changes (git commit)

↓

History Updated with Commit

↓

Repeat for New Changes

↓

View Commit History (git log)

This flow shows how changes are made, staged, committed, and recorded in the repository history.

Execution Sample

Git

git init
echo 'Hello' > file.txt
git add file.txt
git commit -m 'Add file.txt'
git log

Initialize repo, create a file, stage it, commit it, then view commit history.

Process Table

Step	Command	Action	Result
1	git init	Create new empty git repository	Repository initialized with empty history
2	echo 'Hello' > file.txt	Create file.txt with content 'Hello'	file.txt created with text
3	git add file.txt	Stage file.txt for commit	file.txt is now in staging area
4	git commit -m 'Add file.txt'	Commit staged changes with message	New commit created with file.txt content
5	git log	Show commit history	Displays commit with message 'Add file.txt'
6	Exit	No more commands	End of demonstration

💡 No more commands to execute; commit history shows one commit.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
Repository	null	Empty repo created	Empty repo with no commits	Staging area has file.txt	One commit with file.txt	Commit history contains 1 commit
file.txt	Does not exist	Does not exist	Created with 'Hello'	Created with 'Hello'	Created with 'Hello'	Created with 'Hello'

Key Moments - 2 Insights

Why do we need to 'git add' before 'git commit'?

Because 'git add' moves changes to the staging area, and only staged changes are included in the commit, as shown in step 3 and 4 of the execution table.

What does 'git log' show after the first commit?

'git log' shows the commit history including the commit message and metadata, as seen in step 5 where the commit 'Add file.txt' appears.

Visual Quiz - 3 Questions

Look at the execution table, what is the state of the repository after step 3?

A Staging area contains file.txt but no commits yet

B Repository has one commit

C Repository is empty with no files

D file.txt is deleted

💡 Hint

Check the 'Action' and 'Result' columns at step 3 in the execution table.

At which step does the commit history get updated with a new commit?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look for the step where 'New commit created' is mentioned in the Result column.

If you skip 'git add' and run 'git commit' directly, what would happen?

A Commit will include all changes automatically

B Commit will fail or create empty commit if no staged changes

C Repository will be deleted

D file.txt will be removed from disk

💡 Hint

Recall the role of staging area shown in step 3 and 4 of the execution table.

Concept Snapshot

git repository stores committed history.
Use 'git init' to create repo.
Make changes, then 'git add' to stage.
Use 'git commit' to save staged changes.
View history with 'git log'.
Only staged changes are committed.

Full Transcript

This visual execution shows how a git repository records committed history. First, 'git init' creates an empty repository. Then a file is created with content. 'git add' stages the file, preparing it for commit. 'git commit' saves the staged changes as a new commit in the repository history. Finally, 'git log' displays the commit history. The staging area is important because only files added there are included in commits. This process repeats as you make more changes and commits.