We opted for the Fisheye/Crucible combination because we wanted smart commits.
Crucible is having trouble though accurately showing differences in more complex reviews, including reviews of branches where history has been re-written (rebase or a soft reset followed by a re-commit of the resulting files). Several times we have had reviews where files show up that shouldn't, or are innacurately represented (shows changed when it should show new, shows up as new and then show differences). Using our git difftool, the same comparisons are shown correctly.
Does Stash support history rebasing or other history re-write? Has anyone used both and can compare the effectiveness of the "diffing"?
Rebases are shown correctly in Stash pull requests, in the form of "N commits added, M commits removed".
In the history, the only thing visible is the current state.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.