Support the new SonarQube impact severity levels "blocker" and "info"… #10721
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fniessink
force-pushed
the
10708-add-support-for-the-two-new-sonarqube-impactseverities-info-and-blocker
branch
2 times, most recently
from
a28c624 to
40e6e27
Compare
…, introduced in SonarQube v10.8. Closes #10708.
fniessink
force-pushed
the
10708-add-support-for-the-two-new-sonarqube-impactseverities-info-and-blocker
branch
from
40e6e27 to
32add67
Compare
|
fniessink
deleted the
10708-add-support-for-the-two-new-sonarqube-impactseverities-info-and-blocker
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…, introduced in SonarQube v10.8.
Closes #10708.