<!--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=205201) </details> <!--IssueSummary end--> ### Problem to solve Quickly filter the changes in the merge request to only show the files that you own. ### Intended users * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Presley (Product Designer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#presley-product-designer) ### Further details Let's say a new feature has been added and we have a merge request that needs to be approved by both Sasha and Presley where Sasha needs to approve almost everything but Presley only needs to approve the changes in the *.css and *.scss files. In the CODEOWNERS document we can specify that all changes on *.css and *.scss files automatically assign Presley to approve the change. But Presley does not have an easy way in GitLab to view the *.css and *.scss files. ### Proposal Adding a filter to the changes tab in the merge request to only view the files that you're a codeowner of as specified by the CODEOWNERS document. ### Permissions and Security ### Documentation ### Availability & Testing <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### What is the type of buyer? Starter / Bronze and up as those can add CODEOWNERS ### Links / references