Thanks for the suggestion! Interesting rebase operations is something we want to support eventually, though there are a bunch of other things we'll get to first.
I do my interactive rebases via terminal, but 9 out of 10 times, it fails claiming there is an ongoing operation or some other times it claims that the previous process may have crashed.
The only resolution is to restart atom.
I wonder if its related to lack of support or to terminal or something else.
Any ideas?
@the-j0k3r it sounds like you're seeing #961, so you may wish to subscribe there :smile:
Sounds like it. thanks
Would like to second this, we are using pull.rebase=true by default on our systems to have cleaner trees, so this would really be a nice feature to have!
@gromain
How to do "git rebase --continue" after resolving a conflict in atom ?
Most helpful comment
@gromain
How to do "git rebase --continue" after resolving a conflict in atom ?