What is Git - Visual Explanation

Process Flow - What is Git

Start: Create Project Files

↓

Initialize Git Repository

↓

Track Changes with Git

↓

Commit Changes

↓

View History

↓

Collaborate by Sharing Repository

↓

Update and Commit Again

↓

Repeat as Project Grows

This flow shows how Git tracks changes in a project from start to collaboration by saving snapshots called commits.

Execution Sample

Git

git init
# Initialize a new Git repository

git add .
# Stage all files for commit

git commit -m "Initial commit"
# Save snapshot of current files

This code initializes a Git repository, stages all files, and commits them as the first snapshot.

Process Table

Step	Command	Action	Result
1	git init	Create .git folder to track project	Repository initialized, ready to track changes
2	git add .	Stage all current files for commit	Files are marked to be saved in next commit
3	git commit -m "Initial commit"	Save snapshot of staged files	Commit created with message 'Initial commit'
4	git status	Check repository status	No changes to commit, working directory clean

💡 No more commands; repository is set up and initial files are saved

Status Tracker

Variable	Start	After git init	After git add .	After git commit
Repository State	No Git tracking	Git folder created	Files staged for commit	Files committed (snapshot saved)

Key Moments - 2 Insights

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

'git add' tells Git which files to include in the next snapshot. Without adding, 'git commit' saves nothing new. See execution_table step 2 and 3.

What does 'git init' actually do?

'git init' creates a hidden folder (.git) that stores all information Git needs to track changes. It does not save files yet. See execution_table step 1.

Visual Quiz - 3 Questions

Look at the execution table, what is the result after running 'git init'?

A Repository initialized, ready to track changes

B Files are marked to be saved in next commit

C Commit created with message 'Initial commit'

D No changes to commit, working directory clean

💡 Hint

Check the 'Result' column for step 1 in the execution_table

At which step are files actually saved as a snapshot in Git?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the 'Action' and 'Result' columns in execution_table step 3

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

A Git saves all files automatically

B Git saves only previously staged files

C Git shows an error and stops

D Git deletes all files

💡 Hint

Refer to key_moments about the role of 'git add' before 'git commit'

Concept Snapshot

Git is a tool to track changes in project files.
Use 'git init' to start tracking.
Use 'git add' to select files to save.
Use 'git commit' to save snapshots.
Snapshots let you see history and collaborate.

Full Transcript

Git helps you save versions of your project files. First, you create files. Then, you run 'git init' to start a Git repository. This creates a hidden folder to track changes. Next, you use 'git add' to tell Git which files to save. Finally, 'git commit' saves those files as a snapshot with a message. You can check status anytime with 'git status'. This process repeats as you update your project, letting you keep history and work with others.