<!--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=434814) </details> <!--IssueSummary end--> <!-- * Use this issue template for suggesting new docs or updates to existing docs. Note: Doc work as part of feature development is covered in the Feature Request template. * For issues related to features of the docs.gitlab.com site, see https://gitlab.com/gitlab-org/gitlab-docs/issues/ * For information about documentation content and process, see https://docs.gitlab.com/ee/development/documentation/ --> ### Problem to solve Branch and approval rule documentation is presented on a number of pages, and there is no "roadmap" that ties them all together. It's not clear how each feature or sub-feature interacts. - [Push Rules](https://docs.gitlab.com/ee/user/project/repository/push_rules.html) - [Code Owners](https://docs.gitlab.com/ee/user/project/codeowners/) - [Manage and Protect Branches](https://docs.gitlab.com/ee/user/project/repository/branches/#manage-and-protect-branches) - [Default Branch protections](https://docs.gitlab.com/ee/user/project/repository/branches/default.html) - [Protected Branches](https://docs.gitlab.com/ee/user/project/protected_branches.html) - [Merge Request approval rules](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/rules.html) - [Security Approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/rules.html#security-approvals) - [Status checks](https://docs.gitlab.com/ee/user/project/merge_requests/status_checks.html) - [List branch rules for a project (GraphQL API)](https://docs.gitlab.com/ee/api/graphql/branch_rules.html) ### Code entry points #### Git Push - Push Rules #### Edit code in UI - Push Rules? #### When a MR is created - Codeowners ? #### When a MR is merged <!-- * Any concepts, procedures, reference info we could add to make it easier to successfully use GitLab? * Include use cases, benefits, and/or goals for this work. * If adding content: What audience is it intended for? (What roles and scenarios?) For ideas, see personas at https://about.gitlab.com/handbook/product/personas/ or the persona labels at https://gitlab.com/groups/gitlab-org/-/labels?subscribed=&search=persona%3A --> ### Proposal - Create a high level overview of how all these features work together - Cross-link existing pages. ### Who can address the issue <!-- What if any special expertise is required to resolve this issue? --> ### Other links/references <!-- E.g. related GitLab issues/MRs -->