Security policy branch exceptions options shows non-protected branches
Summary
Security policy branch exceptions options shows non-protected branches
Steps to reproduce
- Upload a GitLab Ultimate license
- Navigate to a project => Security & Compliance => Policies => New policy => Scan Result policy => Security Scan
- Select specific branches to apply the scan to. Notice the branches allowed to select
- Select branches for exceptions. Notice the branches allowed to select
Example Project
What is the current bug behavior?
The branch exception selector shows non-protected branches. The branch exception selector does not show the same branches as the specific protected branches selector
What is the expected correct behavior?
The branch exception selector does not show non-protected branches. The branch exception selector shows the same branches as the specific protected branches selector
Relevant logs and/or screenshots
Scenario | Screenshot |
---|---|
Protected branch selector | |
Branch exception selector |
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)
Possible fixes
Edited by Alexander Turinske