<!--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=346826) </details> <!--IssueSummary end--> While investigating https://gitlab.com/gitlab-org/gitlab/-/issues/346166 > Another avenue for investigation is how many merge_request_diff_commit records we're keeping, and whether or not we need to. Is there a point in the lifecycle of a MergeRequest where we can schedule a cleanup worker to delete any related DB records we've identified as extraneous?