Mark individual files as reviewed in code review

Problem to solve

When reviewing a large merge request, it can take several sessions to get through the whole thing.

It would be useful to be able to track what you have/have-not reviewed by marking files reviewed.

Currently I collapse files that I have reviewed, but this state is not persisted through sessions.

Further details

• Currently I collapse files that I have reviewed to track my progress, but this state is not persisted through sessions.

Proposal

• Allow me to in some-way mark a file as reviewed for myself (not for others)
• Persist this state on return visits
• Clear the state when the merge request is updated (perhaps with some intelligence if the file hasn't changed)
• Stretch goal - Allow me to see who else has reviewed a file in order to be able to divide-and-conquer a large merge request with team-mates

What does success look like, and how can we measure that?

• Large merge requests are more approachable to reviewers

Links / references