-
- Downloads
Exclude secret_detection findings from autoresolution
Secret Detection findings should be treated as distinct from other finding types as once they are removed from a branch's HEAD that does not guarantee them to be safe and they require manual resolution, such as rotation of the leaked token since they remain present in the git history. Relates to #223248 Changelog: changed EE: true
parent
ca3aa6e0
No related branches found
No related tags found
Showing
- app/models/concerns/vulnerability_finding_helpers.rb 9 additions, 0 deletionsapp/models/concerns/vulnerability_finding_helpers.rb
- ee/app/services/security/store_report_service.rb 2 additions, 0 deletionsee/app/services/security/store_report_service.rb
- ee/spec/services/security/store_report_service_spec.rb 9 additions, 0 deletionsee/spec/services/security/store_report_service_spec.rb
- lib/gitlab/ci/reports/security/vulnerability_reports_comparer.rb 2 additions, 0 deletions...lab/ci/reports/security/vulnerability_reports_comparer.rb
- spec/models/concerns/vulnerability_finding_helpers_spec.rb 27 additions, 0 deletionsspec/models/concerns/vulnerability_finding_helpers_spec.rb
-
mentioned in merge request kubitus-project/kubitus-installer!306 (merged)
Please register or sign in to comment