Staged vs HEAD

Learn the staged difference with git diff --cached.

Compare staged changes

git diff --cached compares staged changes with the current commit. This allows you to review the changes that will go into the next commit. The --cached option performs the comparison using staged content.

git add index.html
git diff --cached

This command shows staged changes rather than changes that have not been staged.

Comparing with HEAD

HEAD refers to the latest commit at the current position in Git. git diff --cached compares staged changes with the contents of this commit. This lets you see which lines will be added or removed before creating a commit.

git diff --cached

-Old heading
+New heading

Plus and minus signs in the output represent staged changes.

Exercise Display staged differences

Write git diff --cached to compare the current commit with staged changes.

Show example solution

# Sahnelenmiş değişiklikleri göster
git diff --cached

Test yourself

Before creating a commit, you want to compare staged changes with the current commit. Which command should you use?
- git status
- git diff --cached
- git diff
- git log
Show answer

git diff --cached — <code>git diff --cached</code> compares staged changes with the current commit.
Inspect staged differences
```
git diff____ 
```
Show answer
```
git diff--cached 
```
Parts of staged comparison

--cached

Shows staged differences
HEAD

Refers to the current commit
git add

Adds a change to staging
git diff --cached

Compares staging with HEAD

Next lesson: Summary - Diff

We Are Enhancing Your Experience

Cookie Preferences

Strictly Necessary Cookies

Analytical Cookies