2 ms·
This is true, and this is entirely the UI / workflow problem. Git keeps a version for you while you are doing a rebase, so you can say `git rebase --abort` and
by nine_k 4y ago
This is true, and this is entirely the UI / workflow problem.
Git keeps a version for you while you are doing a rebase, so you can say `git rebase --abort` and get back to the preserved state. But it does not keep a log of these, and, more importantly, does not ask you whether you are glad with the end result: you cannot --abort right after a rebase completed without conflicts. One would say that you should explicitly do something like `git rebase commit` (or `git merge commit`) after you have reviewed the result.