<!--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=21366) </details> <!--IssueSummary end--> ### Description A problem we've run into a couple of times now is someone accidentally pushing commits with conflict markers instead of resolving the conflicts. A push rule that detects these and prevents pushing would get these errors caught without needing to wait for CI. ### Proposal Add a new push rule under Settings > Repository > Push rules that prevents pushing of conflict markers inside files ### Links / references gitlab-ce#24480 contains a regex for detecting the markers