Issue #14 resolved
With a simple rebase or squash, the actual reviewed content of the pull-request has not changed. The unapprove should not trigger in these cases, despite the history of the source branch being rewritten, since the actual diff of the pull-request remains identical.
Background: users of my add-on (bit-booster) have been reporting bugs to me because their pull-requests get auto-unapproved after they click on the bit-booster rebase button.
PR #21 fixes this. Also, any fix that uses the strategy outlined in Issue
#15will also fix this.
Fixed in 2.2.0 (Bitbucket Server 4.2-4.14) and 3.0.0 (Bitbucket Server 5.x).