CLI-674 Support impact severity values in --severities filter#447
CLI-674 Support impact severity values in --severities filter#447kirill-knize-sonarsource wants to merge 1 commit into
Conversation
✅ Deploy Preview for sonarqube-cli canceled.
|
Agentic Analysis: Early ResultsAgentic Analysis and Context Augmentation are available on your project. Here are some issues that could have been prevented. Follow the links to learn how to put them into action. 1 issue(s) found across 1 file(s):
Analyzed by SonarQube Agentic Analysis in 3.7 s |
Code Review ✅ ApprovedUpdates the --severities filter to support impact severity values alongside legacy ones. Validation logic prevents conflicting inputs, and request handling is correctly updated to route to the API. OptionsAuto-apply is off → Gitar will not commit updates to this branch. Comment with these commands to change:
Was this helpful? React with 👍 / 👎 | Gitar |
|



Summary by Gitar
--severitiesfilter to support both impact severity values (HIGH,MEDIUM,LOW) and legacy severity values.impactSeveritiesparameter toIssuesSearchParamsand request handlers to correctly route filtered requests to the API.This will update automatically on new commits.