I've been using BitBucket for a few months now, and my team and I seem to struggle much more with pull requests than I've ever seen while using GitHub's interface. I'd really like to know how other teams deal with the concept of a code 'review' and tracking a Pull Request (PR)'s progress.
- When you review a PR, do you try and group your comments into a single 'review'? How?
- Do you ever run into issues with a team member starting to respond to comments and make changes before you've finished going through the code? If so how do you mitigate this?
- When re-reviewing a PR, how do you track the incremental changes since the last time you reviewed?
In GitHub we had the notion of a specific review that was issued on a PR, the PR author could later mark as resolved, and the reviewer could check what had changed between that review and the new state. I'm not sure what the BitBucket-flow looks like.