title: eb deploy --staged usage
body: <p>Back in EB version 2 , when using the git aws.push command, if a push had been done recently, then the next push would not take long at all, I assumed it was only pushing up the changed files, rather than the whole repo.</p>
  
  <p>In Eb version 3, the EB Deploy command appears to upload everything every time. </p>
  
  <p>The Docs say that there is a --staged option </p>
  
  <pre><code>Deploy files staged in the git index instead of the HEAD commit.
  </code></pre>
  
  <p>Is this equivalent to the old way where it would only upload the changed files? or am I misunderstanding how this command should be used. </p>
  
  <p>usually uploading the whole thing is ok, but when a quick fix needs to be made, having a faster way to upload was useful. So I am just after some clarification if the --staged command will do what I think it does, and only upload the changed files from the last push?</p>