title: does --quit leave you with a clean index and worktree after a rebase or a cherry-pick operation?
body: <p>I know that --quit does not change your HEAD pointer, so any commits made successfully during a rebase or cherrypick are still there.</p>
  <p>But what I'm unsure of is, in case a conflict happened during a cherry-pick or a rebase, whether using --quit clear the changes brought about by the conflict, such as the successfully added changes, the conflict markers in the working directory, the multiple versions in the index etc ?</p>
  <p>The <a href="https://git-scm.com/docs/git-rebase#Documentation/git-rebase.txt---quit" rel="nofollow noreferrer">git rebase documentation</a> has the following:</p>
  <blockquote>
  <p>--quit Abort the rebase operation but HEAD is not reset back to the original branch. The index and working tree are also left unchanged as
  a result.</p>
  </blockquote>
  <p>the <a href="https://git-scm.com/docs/git-cherry-pick#Documentation/git-cherry-pick.txt---quit" rel="nofollow noreferrer">cherry-pick documentation</a> is less clear about the effects on the index and work tree:</p>
  <blockquote>
  <p>--quit
  Forget about the current operation in progress. Can be used to clear the sequencer state after a failed cherry-pick or revert.</p>
  </blockquote>
  <p>But this otherwise <a href="https://stackoverflow.com/questions/55431768/whats-different-between-abort-and-quit-as-sequencer-subcommands-for-ch/55433382#55433382">excellent answer</a> in SO has the following:</p>
  <blockquote>
  <p>But if you choose --quit, Git terminates the rebase without moving HEAD, so that you wind up with:</p>
  </blockquote>
  <blockquote>
  <p>but a <strong>clean index and work-tree</strong>. So you don't have to be clever enough to attach a branch name before the --quit.</p>
  </blockquote>
  <p>So which is it ? I know that in a merge --quit will not clear the mess that a merge conflict makes in your index and work tree, it just abandons the merge head state. is it different in case of a cherry pick or a rebase ?</p>