GitLab
Releases
Code quality
Stability
Merge allowed without a passing pipeline
Part of the GitLab project protection check · fix arrives as a guide
What it is
The project does not require pipelines to succeed before a merge request can be merged.
Why it matters
CI becomes advisory. A failing pipeline is a notification rather than a gate, and broken code reaches the default branch whenever someone merges without checking.
How to fix it
Enable "Pipelines must succeed" in the merge request settings, and pair it with "All threads must be resolved" so review comments are not merged past either.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.