Description:
This check verifies that GitLab requires successful pipeline execution before a merge request can be merged into the target branch. Status checks typically include CI/CD pipeline jobs such as builds, tests, security scans, and quality validation checks.
Rationale:
Automated status checks help ensure that code changes are validated before integration. Requiring successful pipelines before merge reduces the risk of introducing defective, unstable, or vulnerable code into protected branches and supports secure software development practices.
Impact:
Enforcing required status checks may:
Prevent merge requests from being merged when pipeline jobs fail.
Increase merge times while validation jobs complete.
Improve code quality and software reliability.
Reduce the likelihood of production issues caused by untested changes.
Default Value:
Disabled
By default, GitLab does not require successful pipelines before merge requests can be merged unless the project is explicitly configured to enforce pipeline success.
Default behavior:
Merge requests may be merged regardless of pipeline status (depending on project settings).
Pipeline success enforcement is not guaranteed.
Remediation:
Test Plan:
Log in to GitLab with access to the project.
Navigate to Settings → Merge Requests.
Locate the Merge Checks section.
Verify that Pipelines must succeed is enabled.
Create a test merge request with a failing pipeline.
Attempt to merge the merge request.
Implementation:
Log in to GitLab with Maintainer or Owner privileges.
Navigate to the target project.
Select Settings → Merge Requests.
Locate the Merge Checks section.
Enable:
Pipelines must succeed
Save the configuration.
Backout Plan:
Log in to GitLab with Maintainer or Owner privileges.
Navigate to Settings → Merge Requests.
Locate the Merge Checks section.
Disable Pipelines must succeed.
Save the changes.
Confirm that project operations are normal after the rollback.
References: