I'm trialing Collaborator Community edition (with the possibility of purchase) and am using it for code reviews of a git version controlled repository that are triggered on BitBucket pull requests.
I've noticed that multiple changesets are uploaded, which depending on the change may include merges with the integration branch. Typically, the integration branch changes have already been reviewed and are not valid for the context of the review being performed, creating extra content that either needs to be ignored or re-reviewed.
Is there any way to ignore the merged changes, or similary, upload changes as a difference against an integration branch?
The only way I have found that may be a solution is create a custom upload script that performs a diff against the intergration branch and create a WebHook in BitBucket.
Thanks for any advice in advance