Freeze particular diffs in pr review

[jmilkiewicz_1]

Hey

I am struggling a way to find the most effective code review for me. 

Imagine following situation Alice created PR with 3 files changed a,b,c and asked Bob to review it.

Bob adds a few comment to Alice changes to file b and c but no comments to changes to file a. As Bob is working on this project in his spare time and is in a different time zone than Alice, it takes about 1-2 days when he gives this PR a review for the 2nd time. He sees than Alice introduced a few new commits to this PR and here is the problem: is there an easy way for him to figure out that all new commits Alice did are NOT changing anything in a file a ( no new changes to that file after he did review for the 1st time)  so he can safely skip checking changes to file a and only focus on files b and c?

I am looking for a way to somehow mark particular changes as "ok" so i do not need  to review them again when new commits to the PR come.

I can imagine doing it in a manual way by taking notes which files are "fine" up to particular commit id, so when new commits come i'd need to figure out if any of them introduced changes to files on "fine" list so i'd need to review them again (+ review files i added comments to) 

Any ideas? 

[Daniil Penkin]

Hello @jmilkiewicz_1,

Thanks for reaching out!

The functionality you described is usually called iterative reviews, and unfortunately it isn't available at the moment in Bitbucket Cloud. There's a ticket in our issue tracker:  please vote for it and watch it so that you get notified when it updates status. We are aware of this use case, and it is somewhere on the roadmap, so stay tuned.

Hope this helps. Let me know if you have any questions.

Cheers,
Daniil