<!--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> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=452330) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=452330) </details> <!--IssueSummary end--> ### Summary In https://gitlab.com/gitlab-org/gitlab/-/merge_requests/147890 we updated the Branch rules details page to use the shared approval rules app. The approval rules app uses a separate endpoint to retrieve the list of approval rules (`<project>/approval_rules` REST API). We can optimise the implementation of the approval rules app on the Branch rules details page by including the approval rules in the Branch rules GraphQL request, this way we don't have to make the separate REST API call to get the list of approval rules. [`ApprovalProjectRule`](https://docs.gitlab.com/ee/api/graphql/reference/#approvalprojectrule) already exists for the GraphQL request, but it does not contain all the fields needed for the Approval rules app to work. **As part of this issue we need to:** 1. Identify the missing fields in [`ApprovalProjectRule`](https://docs.gitlab.com/ee/api/graphql/reference/#approvalprojectrule) (~frontend). 2. Add the missing fields to the [`ApprovalProjectRule`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/app/graphql/types/branch_rules/approval_project_rule_type.rb) type (~backend). 3. Update the GraphQL schema on the frontend to include the new fields (~frontend). 4. Update the approval rules app to accept data from the parent and skip the REST API call (~frontend).