Merge request automatically merged
Summary
I was just merging some branches into eachother that both had merge requests attached. Out of nothing a merge request that had a WIP: in the title, and that had a pipeline still running, was merged. It could not have been a misclick since the merge button is physically blocked. And pipelines must be green.
Is there some undocumented feature (or april 1st) joke programmed into the merge logic?
Steps to reproduce
Not sure how to reproduce, after this happening I could not reproduce this on another merge request
Example Project
What is the current bug behavior?
What is the expected correct behavior?
GitLab should not randomly merge Draft merge requests into eachother when pushing to its branch.
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)