Skip to content

Handle GitLab setting merge request as WIP after pushing

Because of this GitLab feature, we can have the following interaction:

  1. Someone creates a merge request containing a commit with WIP in its name. GitLab doesn't consider the Merge Request as WIP at this point.
  2. Merge request is assigned to Marge; it checks that the merge requests is not WIP and proceeds. 1 The branch is rebased and pushed again.
  3. Because we have just pushed a commit that contains WIP (even if it was in one of the original commits), GitLab marks the merge request as WIP (it even reports "Marge Bot marked as Work In Progress").
  4. After CI passes, she tries to merge, but GitLab now refuses to merge and we fail with "had some issue with gitlab"

We should test for WIP status before merging or, perhaps better, after the merge failed and we don't know why.