Vovodroid

I'm doing test rebase. After closing this window  I get assert  with empty commandOutput. Could it be origin for not continuation of rebase?

Ok, I guess I found the reason, nothing complicated, but I need a hint how to fix this. First, `FormResolveConflicts._thereWhereMergeConflicts` is not involved in scenario in question. After rebasing `EnableButtons()`...

Also we need to close this dialog  as well, if we want the whole rebasing process to be done without unnecessary interactions.

And skip this one (is it Git's own dialog?) 

> Could you add your subscription to `contributors.txt` in a separate PR, please? I still didn't contribute anything))). Should this list contain real name and email? Looking at this ...

> We should turn line 180 of `GetRevision(commitHash, ...)` into @mstv, open PR or you'll do?

> Does the requested revision exist? Sure.

> Git tries to be nice to allow changes to the commit messages after conflicts as the rebase did not go without manual tweaks. But my complaint is about case...

Well, I implemented very dirty solution for continue rebasing https://github.com/vovodroid/gitextensions/commit/436d25e01987c29afe61d6997045b46fd89da46d It can close git cmd window and continue rebasing if it suggests that no error found (though it could now...

> Git is still giving you a chance to tweak the commit because the conflict existed. Git can at least add option to rerere or command line to skip if...