How does mixed reset affect working directory?

That's a very straightforward and important question!

Let's keep it simple:

A mixed reset does NOT affect your working directory.

Here's why and what it means:

• Your working directory is where you see and edit your actual files (e.g., math.js). Think of it as your active workspace or desktop.
• When you perform a git reset --mixed (or just git reset as it's the default), Git will:
  1. Move the HEAD pointer (if you specify a different commit, like HEAD~1).
  2. Update the staging area (or "index") to match the HEAD commit. This means any changes you had staged (with git add) are un-staged.
  3. Leave your working directory completely untouched. The files on your disk will remain exactly as they were before the reset command.

Example from the lab:

1. You added function divide(a, b) { return a / b; } to math.js. This change is in your working directory.
2. You ran git add math.js. Now, the change to math.js is also in your staging area.
3. You ran git reset HEAD.
   • Working directory: The math.js file still contains function divide(a, b) { return a / b; }. It's unaffected.
   • Staging area: The change to math.js is removed from the staging area.

So, after a mixed reset, any changes you had made are still safely in your files in the working directory; they're just no longer marked as "ready to commit." You can then modify them further, or git add them again when you're ready.

It's a very "safe" reset in terms of your actual code files!