You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I was thinking this morning about code reviews. We often have larger refactorings that touch lots of files, often with trivial changes, and it's hard to find time to go through the whole thing in one sitting without being interrupted. After you've been interrupted, it's also hard to know where you were.
How about adding an additional space for code reviews. For simple changes it's OK to just approve directly and comment directly in the PR (as now), but for larger PRs it would be really nice to be able to say 'start code review' and then enter a private space where I can:
The fact that a code review has been started would also show up in the PR, so if someone has already started the review of a large PR other reviewers can see that and avoid duplicate effort.
The state can be defined by file and head revision, so if the PR is updated then modified files revert to 'unreviewed'.
On completion, any open comments can be transferred to the main PR and the review status updated appropriately.
It seems like this should fit with a lot of the existing functionality and interface components, and would help enormously to deal with big PRs as 'trivial' changes can be quickly filtered out, progress is persisted through interruptions, and duplicate work is avoided.