Iterative Reviews in Merge Requests
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
Reviewing a Merge Request often is an iterative process: review the first iteration, then the MR author pushes some changes, reviewers review again, repeat until all discussions are resolved and everybody is happy. In further iterations, reviewers do not want to go through the whole diff again, but rather only review changes since they last reviewed.
Further details
If reviewers can mark a MR as „I reviewed it, but cannot approve it“, then next time allow them to show the diff between the commit at that previous time and the latest commit.
Proposal
Implement functionality similar to Bitbucket which pretty much nails Iterative Reviews:
https://www.atlassian.com/blog/bitbucket/new-features-bitbucket-4-11
What does success look like, and how can we measure that?
Could we measure user satisfaction?