Skip to content

Rework severity catagorization #201

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 59 commits into from
Sep 8, 2023

Conversation

PhilippSalvisberg
Copy link
Collaborator

closes #200

reason: this is most probably a bug and if not
this should be fixed to make it clear.
…tion to make clear that this can reduce the required resources
@sonarqubecloud
Copy link

sonarqubecloud bot commented Sep 8, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@PhilippSalvisberg PhilippSalvisberg merged commit a8a6280 into main Sep 8, 2023
@PhilippSalvisberg PhilippSalvisberg deleted the feature/issue-200-severity-categorization branch September 13, 2023 12:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fix catagorization of guideline severties.
1 participant