Push rule: Reject commits with merge conflicts in source
Recently we had a problem with one of our developers committing a merge conflict, without actually fixing the conflict. This didn't break our build, since it was in an SQL-statement, and wasn't discovered until another developer pulled those changes into their repo and tried to run that specific SQL.
Push Rule to
REJECT commits that contains code like
<<<<<<< HEAD or equivivalent.