<!--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=505432) </details> <!--IssueSummary end--> Right now there's no way to select a specific commit on a [`MergeRequest`](https://docs.gitlab.com/ee/api/graphql/reference/index.html#mergerequest) query and get its stats similar to [`diffStatsSummary`](https://docs.gitlab.com/ee/api/graphql/reference/index.html#diffstatssummary). This is required to fix https://gitlab.com/gitlab-org/gitlab/-/issues/483020+. I see two possible approaches to fix this: ## Option A 1. Allow passing a `commitId` to the `MergeRequest` query. This approach is similar to how our REST API works but doesn't align well with GraphQL's resource structure. ## Option B 1. Add a [`commit`](https://docs.gitlab.com/ee/api/graphql/reference/index.html#commit) field to [`MergeRequest`](https://docs.gitlab.com/ee/api/graphql/reference/index.html#mergerequest) query (`commits` won't work as it's pagination based) 1. Add a `commitId` argument for `Commit` query 2. Provide commit stats field in the same shape as [`diffStatsSummary`](https://docs.gitlab.com/ee/api/graphql/reference/index.html#diffstatssummary) This option aligns better with GraphQL's paradigm but requires more effort to implement.