Add setting to allow merge on skipped pipeline
What does this MR do?
Since #30059 (closed) (!18838 (merged)), it is no longer possible to merge with skipped pipelines.
This MR adds a setting to allow this (like previous Gitlab versions).
Fixes: #211482 (closed)
Screenshots
Comment | a. Settings > General | b. Pipeline passed |
c. Pipeline failed |
d. Pipeline skipped |
---|---|---|---|---|
1. All disabled | ||||
2. Pipelines must succeed | ||||
3. Pipelines must succeed + Skipped pipelines are allowed |
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides - [-] Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. - [-] Tested in all supported browsers
- [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
- [-] Label as security and @ mention
@gitlab-com/gl-security/appsec
- [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
- [-] Security reports checked/validated by a reviewer from the AppSec team
Edited by 🤖 GitLab Bot 🤖