<!--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=375632) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=375632) </details> <!--IssueSummary end--> The following discussion from !98686 should be addressed: - [ ] @hfyngvason started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/98686#note_1116479981): (+1 comment) > Thanks @j.seto! The code looks good, but I am wondering why this was needed in the first place. I would have expected all git access to be subject to the same checks (for example, [this code](https://gitlab.com/gitlab-org/gitlab/-/blob/3eb5d6d1c81705076015d2110acb91e61cbbbe98/ee/lib/ee/gitlab/checks/push_rules/commit_check.rb#L43) also validates commit messages), but evidently merge request merges implement their own set of validations. This seems bound to lead to further inconsistencies such as here (and I bet we already have several). > > Do you know why we have this duplication?