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?
