Allow merges in the absence of a pipeline
What does this MR do and why?
Prior to this change, MRs without pipelines could not be merged in projects with "Pipelines must succeed" enabled. But this was unexpected. For example:
- Projects without a
.gitlab-ci.yml
could get blocked because of a group-level setting. - Users of
rules
who intentionally filtered out jobs for a given change needed to have a "dummy" job just to merge in such cases.
See #334281
Changelog: changed
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
- Enable Pipelines must succeed in a project without a
.gitlab-ci.yml
- Create a merge request
- The Merge button should be visible
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Hordur Freyr Yngvason