In a repository there is usually folders that correspond to a certain class of programming. Either frontend, backend (or maybe more specific than that). For example in Ruby on Rails `app/assets` is entirely frontend related while `app/models` is entirely backend. I propose that we enable the possibility of adding a file in a repository where the user can mark certain folders as being frontend, backend, etc. This would enable us to filter the changes by backend or frontend only in a Merge request. Which can remove a lot of clutter from a review or even while developing a feature. @DouweM showed me [Suggest approvers based on code owners](https://gitlab.com/gitlab-org/gitlab-ee/issues/5382) and I think this feature couples well with the one linked. Note: I am using frontend and backend as examples, ideally we could separate the folders in our repository by any categories we deem fit. Thoughts @JobV @DouweM ? ### Proposal Add support for including labels in the CODEOWNERS file, and suggest those labels when creating/editing a merge request. For example, `app/models` could have the label gitlab-ce~2492649 which would automatically add that label, notify any label subscribers, and make it appear on the merge request list when filtered by gitlab-ce~2492649 ### Links / references