<!--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=423750) </details> <!--IssueSummary end--> ### Proposal This comes from this [ZD ticket](https://support.gitlab.com/hc/en-us/requests/444515). I'm proposing that, where applicable, pre-receive hook error messages list offending commits. For example, for the push rule setting "Require expression in commit messages", it may be the case that an offending push has some commits with passing messages and others with failing messages. For example, instead of this: > GitLab: Commit message does not follow the pattern '(TFS#\\d+;)|(JIRA#\[A-Za-z0-9\]{2,}-\\d+;)' Maybe this: > GitLab: One or more commit messages do not follow the pattern '(TFS#\\d+;)|(JIRA#\[A-Za-z0-9\]{2,}-\\d+;)' > > 1b9a2ca9d1b8b87cc50ba741217cf29c50f27855