This an actionable insight from the [Code Review FY21-Q2 Category Maturity Scorecard](https://gitlab.com/gitlab-org/ux-research/-/issues/941) research ([insight](https://dovetailapp.com/projects/ac5e32e9-616d-4ddd-a1bb-1eb49084fe4e/insights/present/612e13a7-6878-4677-8a9f-35c16b42801c)). ### What Help users better understand the CODEOWNERS file format and prevent errors in file creating/maintenance. GitLab relies on a CODEOWNERS file for a number of different features. Users must find the documentation on their own to understand how to best format the file so that it’s valid for GitLab to read. ### Why So that users are more familiar with the correct syntax and possibilities of the CODEOWNERS file, avoiding errors and wasted time. ### How - [x] https://gitlab.com/groups/gitlab-org/-/epics/10057+ - [x] https://gitlab.com/groups/gitlab-org/-/epics/10060+ - [ ] https://gitlab.com/groups/gitlab-org/-/epics/9819+ - [x] https://gitlab.com/groups/gitlab-org/-/epics/10058+ <!-- 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 -->