Design: Summarize proposed changes in a merge request
Based on the learnings and early insights from the first iteration of summarizing changes here- Internal Feedback
Problems to Address
• The comment appears in a random place in the merge request, and there are multiples of them. (Not grouped)
• There is no attribution to who (requested) or what (event) triggered the summary
• The summary is not a replacement for the detailed description of what was changed in the merge request.
Insights:
Make the summary more contextually relevant to users
Goals:
For the reviewer
• When the review is requested: Provide the summary in To-Do's/Email notification
• On the MR page: Provide a history of summaries of those changes
For the author
• Declutter: when another review round happens we could send a single email to the author with a brief summary of all the changes instead of sending one email per review comment.
• Group reviewer comments on topics and higher-level ideas, sort topics by importance