Merge conflicts notifications/todos
Large/disruptive MRs quite often take a while to get merged as reviewers are more efficiently focusing on smaller MRs on top of the fact that reviewers must be diligent with their approvals. Large/disruptive MRs are also prone to merge conflicts as their changes span over a number of locations.
When completing an MR and assigning it to a reviewer, these MRs can often gain merge conflicts that are no longer visible through 'MRs assigned to me' views, like the default
/dashboard/merge_requests view. This can further delay the merge of these MRs as when the reviewer is ready to tackle this large/disruptive MR, they are met with merge conflicts which must be passed back to the author.
Send a notification/todo to the author of an MR when a merge conflict arrises. Just like how we notify the MR author of any failed builds. This way, hopefully, the author can tend to the merge conflicts before the reviewer starts their review process.