Follow-up from "Resolve "Squash commit message does not honor regex settings""

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Work on this issue
• Close this issue

The following discussion from !98686 (merged) should be addressed:

• @hfyngvason started a discussion: (+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 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?