Coverage-Check Approval Rules always requires approval regardless coverage percentage changes
Summary
When enabling the Coverage-Check Approval rule the expected behavior of requiring approvals only when coverage decreases does not seem to work. Approvals are required by this check at all times regardless of coverage changes.
Steps to reproduce
Create a dummy project with CI to echo out a coverage percentage. Create a MR and decrease the coverage.
Example Project
Unable to provide an example project on gitlab.com since approvals are optional. For example this project: https://gitlab.com/kang.sung/code-coverage-test does not reflect the bug. It seems like all approvals are optional regardless of how the coverage-check is triggered or not.
What is the current bug behavior?
Coverage-Check approvals are required at all times regardless of coverage percentage.
What is the expected correct behavior?
Coverage-Check approvals are only required when coverage decreases.
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)