Interactive rebase for squashing pull request ALWAYS aborting.

[Morgan Kita]

This is with Sourcetree for Windows 1.6.8.0

So I've tried to create a workflow between sourcetree and stash, where you can work on a feature branch, create a pull request from it, make changes to satisfy commentators in a code review, and then SQUASH those changes (or even changes from the branch) at the end to avoid cluttering the history.

More or less then would give you one entry in this history from merging the feature into main.

However, when I try to do this using sourcetree with "interactive rebase" by simply squashing the commits, if there are any conflicts at all between entries in the history of the feature branch (though the combined state certainly has no conflicts), then it fails saying it can't apply one of the conflicting commits onto one of the earlier ones.

With my understanding of Git this expected (though should be something you can automate as the final state has no conflicts), but the problem is instead of letting me resolve the conflicts and continue the rebase (doesn't matter if I click "amend commit" or not), IT ABORTS EVERY TIME once I click ok!

I saw one other post here about that suggesting you can use the terminal before hitting ok as a workaround, but this isn't really acceptable. Is this bug or an unfinished feature?

Any other workarounds?

[Morgan Kita]

This was supposed to be fixed in 1.6, but appears to still be an issue.

I have a new bug open @ https://jira.atlassian.com/browse/SRCTREEWIN-2493

[jacek545]

Is there anything happening around that bug? It is over a year when it was found and the issue still exists in 1.6.22

[Marcel Bradea]

Any resolution on this?

This seems to still be happening as of mid-2016 (SourceTree Windows 1.8.3) !!!
This completely removes the usefulness of the crucial interactive rebase feature. What's the current workaround for this?

[Seth]

Here's a workaround from the bug report that Morgan posted. Workaround was shared by Joe D:

I found a slightly better workaround:
1. Just close SourceTree entirely by right clicking on the taskbar button and clicking Close. (Don't click the Close button on the error message)
2. Re-open SourceTree and resolve the conflicts, then Commit. (the commit message will have to be entered manually - another bug)
3. Click Actions > Continue Rebase.
(repeat as above for any additional conflicts)

[edmtgarcia]

Workaround works, but is quite odd.

Any changes on this?

[Seth]

You can definitely create a new bug. Seems appropriate. Post the link to it as an answer to this question to help others find it and vote for it.

[Morgan Kita]

Huh, well it's clearly broken again. Maybe something different about my use case, I guess I should make a new bug on jira? Assuming I can, not sure how that works for Atlassian.

[Seth]

This was supposed to be fixed in 1.6, according to https://jira.atlassian.com/browse/SRCTREEWIN-1880