Unmergeable MRs with [skip ci] and "Pipelines must succeed"
In repositories that have the "Pipelines must succeed" setting enabled, merge requests that make use of "[skip ci]" cannot be merged without doing a force push, adding another commit or disabling "Pipelines must succeed".
Steps to reproduce:
- Create a Gitlab project with the "Pipelines must succeed" setting enabled and a CI pipeline
- Open an MR with a single commit that uses [skip ci]
https://gitlab.com/cmd_h/skip-ci-unmergeable/-/merge_requests/1
It looks like this behaviour is happening since the changes in #30059 (closed).
Expected Behaviour:
I would expect that either [skip ci] is ignored when "Pipelines must succeed" is enabled or that I could at least trigger a manual pipeline to get my MR merged. As it stands I either need "Owner" permissions for the repository to change the "Pipelines must succeed setting" temporarily or do some workarounds in git to get the MR "mergeable".
The following docs also seem outdated in this regard, as they make it sound like [skip ci] would always work: