title: What should happen after git rebase --continue?
body: <p>So I did a git rebase, got merge conflicts which I corrected and then did git adds on each file. At this point I did git rebase --continue and there were no more conflicts. But when I did a git status I saw there was nothing left to add. Did it create a commit already? I tried git commit but was not prompted for a commit comment. What should I do next?</p>
  
  <p><strong>EDIT:</strong> One further point -- when I did the rebase it said: "rebase in progress; onto 1be...000" and then it showed me many modified (merged) files (as well as stop when a merge conflict arose). I have looked at the commit 1be... and I see none of these automatically merged files or any that I resolved the conflicts for. So I would like to find these files since the manually modified files must be reviewed -- I need to specify a commit to be reviewed.</p>
  
  <p>EDIT: Just to clarify, I am puzzled at what happens after all the merge conflicts are done, that is, I edited all the files and added them and the continued with the rebase until no more merge conflicts were reported. There are some files that I had never modified before that I expected to see if I did a commit which as mentioned I tried. My next step is to submit this commit for review but it doesn't seem like the reviewer will see all the files I merged.</p>
  
  <p>Is it possible he doesn't need to see files that match those on the branch I was merging with?</p>