When you right click on a specific commit and execute "rebase children of {hash} interactively...", I can usually get a dialog where I manage commits EXCEPT when there are multiple branches at the same commit I right-clicked on.
So my typical resolution is to temporary delete branches like dev / master so that there are only one or two branches at the same commit that I'm trying to rebase from.
I don't see any reason why this should happen. Rebasing on the indicated commit should not be influenced by the branch or branches which that commit is the endpoint of. Interestingly, multiple branches ending at the branch being rebased (rather than the branch being rebased to), works as expected.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've observed the same behavior, and didn't connect that the presence of multiple branches was causing it, until I read this post. Note that both interactive rebase and normal rebase have the same problem. Note also this is still happening in Sourcetree 4.0 (232) as of 1/8/20, using Catalina 10.15.2.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Elisha, can you let us know which OS and SourceTree version are you using so we can try and reproduce this issue here?
Best regards,
Ana
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.