<!--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=205262) </details> <!--IssueSummary end--> The following discussion from !24168 should be addressed: - [ ] @nick.thomas started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/24168#note_286157846): (+2 comments) > We have `MergeRequestContextCommit` and `MergeRequestContextDiff` now, too, which would need covering with the same safety. More context: With `BulkInsertSafe` we are able to declare that a model class is safe for use with bulk-insertion to postgres. We identified two more recent model classes that could probably benefit from this. We noticed that they also currently are not considered in import/exports, and we should find out if they should, and whether they could then also be bulk-inserted.