Specify files for the reviewer to focus on in the code review
<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=471183) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal From https://gitlab.com/gitlab-org/gitlab/-/issues/430123#note_1976603830 > In https://gitlab.com/groups/gitlab-org/-/epics/12878 we've built a new reviewer assignment that helps users focus on selecting the right reviewer based on approval rules. However, we [didn't go beyond assignment](https://gitlab.com/gitlab-org/gitlab/-/issues/441689#note_1775054231 "[Design] Incorporate approval rules when assigning reviewers to a merge request") and back into the sidebar and state of the MR. It would be good as you're thinking about the review flow pieces, how we could surface "WHAT" a reviewer has been asked to review. There are levels to this from an author specifying which files they want focus on from a reviewer to using CODEOWNERS to automatically highlight files that match that reviewers assignment. <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->
issue