title: Rebasing a branch changing contents of a newly added file which has no conflicts
body: <p>Is there an instance where when rebasing a branch with let's say <code>origin master</code> results in contents of a newly created file (that has no conflicts since it's new) in that branch changing? If so, what could be the reason for that?</p>
  
  <p>I had three commits on the branch I was rebasing with origin master. I began by checking out a new branch for my new work and added content in a newly created file on the new branch then committed those changes, first-commit, I added more content to the same file and committed second-commit, then I added more content to the same file and committed again third-commit, hence the three commits. So when I tried to rebase, the HEAD went to the first-commit I made and so the contents of the file changed to how it was on the first commit, so when I finished rebasing, the other two commits second-commit and third-commit were replayed on top and my file contents were as they were before I began the rebase.</p>
  
  <p>I'm not sure whether git goes to the first commit on a branch when rebasing that branch and hides the rest of the commits on that branch until the rebase is done.</p>