Git/Gitlab: Is there a built-in way to enforce custom requirements before merging?

Viewed 71

I'd like to prevent any branch that meets certain conditions from being merged into "master", e.g. if the branch would add the string "//BLOCKER", the merge must abort.

I've accomplished this on my own machine with a bash alias, but is there any built-in way in gitlab (or even git itself) to enforce it on a project wide level?

The only approach I could think of was to make the CI pipeline fail on such a condition, but this would make pre-merge testing harder.

1 Answers
Related