🛠️ Mastering Git Reset: A Guide to Undoing Changes

The git reset command is your "time machine" for local development. It allows you to move the HEAD pointer to a specific state in your project's history.

🏗️ The Three Trees of Git

To understand reset, you must know what it's actually moving:

⚙️ The Three Reset Modes

git reset can be called in three ways, each affecting a different combination of the "trees" above.

1. --soft (The Surgeon)

Moves the HEAD, but leaves your files and staging area exactly as they were.
* Use Case: You committed, but forgot to add a file or want to fix the commit message.
* Result: Changes from the "undone" commit are still staged.

2. --mixed (The Default)

Moves the HEAD and resets the staging area, but keeps your files.
* Use Case: You want to "unstage" everything and start your git add process over.
* Result: Changes are kept on disk but appear as "unstaged".

3. --hard (The Wrecking Ball) ⚠️

Moves the HEAD and overwrites everything to match the target commit.
* Use Case: You’ve made a mess and want to completely discard your current work.
* Result: All uncommitted changes in your files are deleted permanently.

📊 Summary Comparison

💻 Common Commands & Examples

Undo the last commit (keep your work)

git reset --soft HEAD~1