<!--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=494469) </details> <!--IssueSummary end--> Describe what you would like to see improved. If you have a CODEOWNERS file in the main directory and [Allowed to push](https://docs.gitlab.com/ee/user/project/repository/branches/protected.html#require-code-owner-approval-on-a-protected-branch) is **not** selected on protected branches we should show a message in the UI. See [Zendesk internal ticket](https://gitlab.zendesk.com/agent/tickets/570462) Currently, we have this in the docs in a couple of places. [Require code Owner approval](https://docs.gitlab.com/ee/user/project/repository/branches/protected.html#require-code-owner-approval-on-a-protected-branch) and [Setup codeowners](https://docs.gitlab.com/ee/user/project/codeowners/#set-up-code-owners). But I think this could be an easy quality-of-life fix if Gitlab sees a CODEOWNERS file and this setting is **disabled** we could provide a banner to tell them to enable code owners in protected branches on the main page. Rather than have customers look through our docs for what is really an easy fix.  To enable Code Owner’s approval on branches that are already protected: - On the left sidebar, select Search or go to and find your project. - Select Settings > Repository. - Expand Protected branches. - Select Add protected branch. - In the list of protected branches, next to the branch, turn on the Code owner approval toggle.