Why version control matters in Git - See It in Action

Why Version Control Matters

📖 Scenario: You are working on a simple text file project with a friend. You want to keep track of changes so you can see what was added or fixed and avoid losing work.

🎯 Goal: Learn how to create a git repository, add a file, commit changes, and see the history of changes to understand why version control is important.

📋 What You'll Learn

Create a new git repository

Add a file named notes.txt with initial content

Commit the file with a message

Make a change to notes.txt and commit again

View the commit history

💡 Why This Matters

🌍 Real World

Version control is used by developers to keep track of changes in code and documents. It helps teams work together without overwriting each other's work.

💼 Career

Knowing git is essential for software development, DevOps, and many IT roles. It shows you can manage projects safely and collaborate with others.

1

Initialize a Git Repository and Create a File

Run the command git init to create a new git repository. Then create a file named notes.txt with the exact content Hello, this is my first note.

Git

# Run 'git init' to start a new repository
# Create 'notes.txt' with the text 'Hello, this is my first note.'

Hint

Use git init to start version control in your folder. Use echo to create the file with the exact text.

2

Add the File to Git and Commit

Use git add notes.txt to stage the file. Then commit it with the message Initial commit with notes.txt using git commit -m.

Git

git init

echo "Hello, this is my first note." > notes.txt
# Add 'notes.txt' to git and commit with message 'Initial commit with notes.txt'

Hint

Use git add to tell git which files to track. Use git commit -m "message" to save a snapshot with a message.

3

Modify the File and Commit the Change

Add the line This is an added line. to notes.txt. Then stage and commit this change with the message Added a new line to notes.txt.

Git

git init

echo "Hello, this is my first note." > notes.txt

git add notes.txt

git commit -m "Initial commit with notes.txt"
# Add a new line to 'notes.txt' and commit with message 'Added a new line to notes.txt'

Hint

Use >> to append a line to the file. Then add and commit the change with a clear message.

4

View the Commit History

Run the command git log --oneline to see the list of commits with their messages.

Git

git init

echo "Hello, this is my first note." > notes.txt

git add notes.txt

git commit -m "Initial commit with notes.txt"

echo "This is an added line." >> notes.txt

git add notes.txt

git commit -m "Added a new line to notes.txt"
# Run 'git log --oneline' to view commit history

Hint

The git log --oneline command shows a short list of commits with their messages. You should see both commits listed.

Practice

1. Why is version control important when working on a project?

easy

A. It deletes old files automatically.

B. It makes your computer run faster.

C. It saves changes step-by-step so you can go back if needed.

D. It changes your code to fix errors without your input.

Solution

1. Step 1: Understand the purpose of version control

   Version control keeps a history of all changes made to files, allowing you to review or revert to previous versions.

2. Step 2: Identify the correct benefit

   Among the options, only saving changes step-by-step matches the main purpose of version control.

3. Final Answer:

   It saves changes step-by-step so you can go back if needed. -> Option C

4. Quick Check:

   Version control = saves changes step-by-step [OK]

Hint: Version control = saving history of changes [OK]

Common Mistakes:

• Thinking version control speeds up the computer
• Believing it deletes files automatically
• Assuming it fixes errors without user action

2. Which git command is used to save your changes to the version history?

easy

A. git commit

B. git push

C. git clone

D. git status

Solution

1. Step 1: Identify commands related to saving changes

   In git, 'git commit' records changes to the local repository as a snapshot.

2. Step 2: Differentiate from other commands

   'git push' sends commits to a remote, 'git clone' copies a repo, and 'git status' shows current state.

3. Final Answer:

   git commit -> Option A

4. Quick Check:

   Save changes = git commit [OK]

Hint: Commit means save changes locally [OK]

Common Mistakes:

• Confusing 'git push' with saving locally
• Using 'git clone' to save changes
• Thinking 'git status' saves changes

3. What will be the output of the command git status after you modify a file but before committing?

medium

A. "Changes not staged for commit:" followed by the modified file name

B. "nothing to commit, working tree clean"

C. "fatal: not a git repository"

D. "Your branch is up to date with 'origin/main'" only

Solution

1. Step 1: Understand git status behavior after file modification

   When a file is changed but not staged, git status shows "Changes not staged for commit:" with the file name.

2. Step 2: Eliminate other outputs

   "nothing to commit" means no changes; "fatal" means not in a git repo; "Your branch is up to date" appears but not alone if changes exist.

3. Final Answer:

   "Changes not staged for commit:" followed by the modified file name -> Option A

4. Quick Check:

   Modified but unstaged = Changes not staged message [OK]

Hint: Modified files show 'Changes not staged' in git status [OK]

Common Mistakes:

• Expecting 'nothing to commit' when files changed
• Confusing error messages with normal status
• Ignoring unstaged changes in output

4. You accidentally committed a file with a typo in the commit message. Which command fixes the last commit message without changing the files?

medium

A. git checkout -- .

B. git reset --hard

C. git revert HEAD

D. git commit --amend

Solution

1. Step 1: Identify command to change last commit message

   'git commit --amend' lets you edit the last commit message without changing files.

2. Step 2: Understand other commands

   'git reset --hard' discards changes, 'git revert HEAD' creates a new commit undoing last, 'git checkout -- .' resets files.

3. Final Answer:

   git commit --amend -> Option D

4. Quick Check:

   Fix last commit message = git commit --amend [OK]

Hint: Amend fixes last commit message only [OK]

Common Mistakes:

• Using reset and losing changes
• Reverting creates new commits, not editing
• Checkout resets files, not commit messages

5. A team is working on the same project. Without version control, what problem is most likely to happen?

hard

A. They will have unlimited storage for all files.

B. They will lose track of who changed what and may overwrite each other's work.

C. The code will run faster on all machines.

D. The project will automatically update on all computers.

Solution

1. Step 1: Understand team collaboration challenges without version control

   Without version control, team members can overwrite each other's changes and lose track of who did what.

2. Step 2: Evaluate other options

   Automatic updates, faster code, or unlimited storage are unrelated to version control.

3. Final Answer:

   They will lose track of who changed what and may overwrite each other's work. -> Option B

4. Quick Check:

   Team work without version control = overwrite risk [OK]

Hint: Version control prevents overwriting teammates' work [OK]

Common Mistakes:

• Thinking version control speeds up code
• Believing it provides automatic updates
• Assuming it gives unlimited storage