Repository (committed history) in Git - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a repository in Git?

A repository is a storage space where your project files and their entire history of changes are saved. It keeps track of all versions of your files.

beginner

What does git commit do?

It saves a snapshot of your current changes to the repository's history. Think of it like taking a photo of your project at a moment in time.

beginner

Why is committed history important?

Committed history lets you see what changed, when, and who changed it. It helps you fix mistakes by going back to earlier versions.

intermediate

What is a commit hash?

A commit hash is a unique ID for each commit. It looks like a long string of letters and numbers and helps you find that exact snapshot later.

beginner

How can you view the committed history in Git?

Use the command git log to see a list of commits with details like author, date, and message.

What command saves your changes to the Git repository history?

A git clone

B git push

C git commit

D git status

git commit saves your changes as a snapshot in the repository history.

What does the commit hash represent?

A A unique ID for each commit

B The size of the repository

C The name of the branch

D The current working directory

The commit hash uniquely identifies each commit snapshot.

Which command shows the list of past commits?

A git branch

B git log

C git add

D git init

git log displays the commit history.

Why is committed history useful?

A To track changes and fix mistakes

B To delete files permanently

C To speed up your computer

D To create new files automatically

Committed history helps track changes and revert to earlier versions if needed.

What happens if you don’t commit your changes?

A Repository is deleted

B Changes are automatically saved

C Git creates a new branch

D Changes are not saved in history

Without committing, changes remain only in your working area and are not saved in the repository history.

Explain what a Git repository's committed history is and why it matters.

Think about how saving versions of a document helps you go back if needed.

Describe the role of the git commit command in managing repository history.

Imagine taking a photo of your project to remember its state.