What is Git - Quick Revision & Key Takeaways

Recall & Review

beginner

What is Git?

Git is a tool that helps you save and track changes in your files, especially code. It lets many people work together without losing any work.

beginner

Why do developers use Git?

Developers use Git to keep a history of their work, fix mistakes easily, and work with others smoothly by sharing changes.

beginner

What is a repository in Git?

A repository is like a folder where Git keeps all your files and the history of changes made to them.

beginner

What does 'commit' mean in Git?

A commit is like taking a snapshot of your files at a moment in time. It saves your changes so you can look back or share them.

beginner

How does Git help when multiple people work on the same project?

Git helps by keeping track of everyone's changes separately and then combining them safely, so no work is lost.

What is the main purpose of Git?

A To track changes in files and help collaboration

B To write code faster

C To design websites

D To run applications

Git is mainly used to track changes and help multiple people work together on files.

What is a 'commit' in Git?

A A programming language

B A type of error

C A saved snapshot of your files

D A user account

A commit saves your current work as a snapshot you can return to later.

What is a Git repository?

A A programming tool

B A folder that stores files and their history

C A type of computer

D A web browser

A repository is where Git keeps your files and tracks changes.

How does Git help teams work together?

A By tracking everyone's changes and combining them safely

B By deleting old files automatically

C By sending emails to team members

D By running tests on code

Git tracks changes from different people and merges them to avoid losing work.

Which of these is NOT a feature of Git?

A Tracking file changes

B Helping multiple people collaborate

C Saving snapshots of work

D Designing graphics

Git does not design graphics; it manages file changes and collaboration.

Explain in your own words what Git is and why it is useful.

Think about how Git helps when many people work on the same files.

Describe what a commit and a repository are in Git.

Imagine taking photos of your work and keeping them in a special folder.

Practice

1. What is the main purpose of Git?

easy

A. To create websites from scratch

B. To edit images and videos

C. To save and track changes in files over time

D. To manage computer hardware settings

Solution

1. Step 1: Understand Git's role

   Git is a tool designed to save and track changes in files, especially code files.

2. Step 2: Compare options

   Options B, C, and D describe tasks unrelated to Git's main function.

3. Final Answer:

   To save and track changes in files over time -> Option C

4. Quick Check:

   Git = tracks file changes [OK]

Hint: Git tracks file changes, not edits or hardware [OK]

Common Mistakes:

• Confusing Git with editing software
• Thinking Git manages hardware
• Believing Git builds websites

2. Which of the following is the correct command to start a new Git repository?

easy

A. git start

B. git init

C. git create

D. git begin

Solution

1. Step 1: Recall Git commands

   The command to create a new Git repository is git init.

2. Step 2: Check other options

   Commands like git start, git create, and git begin do not exist in Git.

3. Final Answer:

   git init -> Option B

4. Quick Check:

   Initialize repo = git init [OK]

Hint: Use 'git init' to start a repo, others are invalid [OK]

Common Mistakes:

• Using 'git start' instead of 'git init'
• Confusing command names
• Trying commands that don't exist

3. What will be the output of the command git status right after running git init in a new folder?

medium

A. No commits yet, nothing to commit, working tree clean

B. Error: repository not found

C. All files are staged for commit

D. Untracked files present, please add them

Solution

1. Step 1: Understand 'git init' effect

   Running git init creates an empty Git repository with no commits.

2. Step 2: Check 'git status' output

   Right after init, git status shows "No commits yet" and "working tree clean" because no files are added or changed.

3. Final Answer:

   No commits yet, nothing to commit, working tree clean -> Option A

4. Quick Check:

   git status after init = no commits, clean [OK]

Hint: After init, status shows no commits and clean tree [OK]

Common Mistakes:

• Expecting errors after init
• Thinking files are staged automatically
• Assuming untracked files message appears immediately

4. You ran git add file.txt but forgot to commit. What will git status show?

medium

A. Changes to be committed: new file: file.txt

B. No changes detected

C. Untracked files: file.txt

D. Error: file.txt not found

Solution

1. Step 1: Understand 'git add' effect

   Running git add file.txt stages the file for commit but does not commit it yet.

2. Step 2: Check 'git status' after add

   git status will show the file under "Changes to be committed" because it is staged.

3. Final Answer:

   Changes to be committed: new file: file.txt -> Option A

4. Quick Check:

   git add stages files, status shows staged changes [OK]

Hint: Added files show as staged, not committed yet [OK]

Common Mistakes:

• Thinking add commits files
• Expecting untracked files after add
• Assuming no changes after add

5. You want to save your changes permanently in Git. Which sequence of commands should you run?

hard

A. git init then git push

B. git commit -m "message" then git add .

C. git status then git push

D. git add . then git commit -m "message"

Solution

1. Step 1: Stage changes with 'git add'

   You first use git add . to stage all changes in the current folder.

2. Step 2: Commit staged changes

   Then run git commit -m "message" to save the staged changes permanently with a message.

3. Final Answer:

   git add . then git commit -m "message" -> Option D

4. Quick Check:

   Stage then commit = add then commit [OK]

Hint: Always add before commit to save changes [OK]

Common Mistakes:

• Committing before adding files
• Using push without commit
• Initializing repo unnecessarily