title: How come git status detects changes, after performing git reset --mixed <commit id>?
body: <p>I'm breaking my head in an attempt to understand how git reset works. I've read various articles, played with my demo repo - and i still don't get exactly what's going on there. When i do git reset --hard, the result is intuitive for me("everything" just goes back to the way it was in that specified commit), but when i do the default git reset --mixed, that's where my confusion begins.</p>
  
  <p><a href="https://www.atlassian.com/git/tutorials/resetting-checking-out-and-reverting" rel="nofollow noreferrer">resetting-checking-out-and-reverting</a>  This is what this article says about git reset --mixed: </p>
  
  <blockquote>
    <p>The staged snapshot is updated to match the specified commit, but the working directory is not affected. This is the default option.</p>
  </blockquote>
  
  <p>My understanding is, that this would mean that git status will detect <strong>no changes</strong>, being that the staged snapshot is now "updated to match the specified commit...".</p>
  
  <p>To my surprise, git status actually shows unstaged changes, corresponding to the <strong>last commit</strong>, before the git reset --mixed.</p>
  
  <p>I assume i'm getting something totally wrong here, and would appreciate it if someone will explain me this issue in simple words, because reading all those articles and posts didn't do the trick :D</p>