Large organizations with many projects and large projects need to enforce review policies so that they can ensure the correct teams and individuals review changes that impact them. File owners will be automatically added to related Merge Requests (separate feature), but it is also necessary to add controls to prevent changes directly to important branches without approval. We should continue to improve on the first iteration of code owners https://gitlab.com/groups/gitlab-org/-/epics/77 ### Vision GitLab is a Git focussed product and we like simple solutions. The code owners approach first implemented by GitHub is a Git based solution that is simple, flexible and reuses the same format as `.gitattributes`. ### Proposal * Make it easy to setup code owners * Validate the contents of the code owners file * Scale to support multiple code owners files for large monorepos ### Links / references - https://blog.github.com/2017-07-06-introducing-code-owners/ - https://git-scm.com/docs/git-check-attr <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->