Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 35,040
    • Issues 35,040
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,246
    • Merge Requests 1,246
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #211482

Closed
Open
Opened Mar 17, 2020 by Dominik Horb@cmd_h

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:

  1. Create a Gitlab project with the "Pipelines must succeed" setting enabled and a CI pipeline
  2. Open an MR with a single commit that uses [skip ci]

cmd_h/skip-ci-unmergeable!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:

https://docs.gitlab.com/ee/ci/yaml/#skipping-jobs

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab#211482