-
-
Notifications
You must be signed in to change notification settings - Fork 529
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
[Gitlab] Filtering by severity which issues are added to MR #135
Comments
Filtering by severity which issues are added to MR
Limiting the number of reported issues sounds reasonable, providing it's then clear in a summary or comment that the output is truncated. Does filtering not still cause an issue with the quality gate failing but issues not being decorated? |
implemented a filter system with 3 filters (maxamount,severy,type) added commentfilter to the githubpullrequest decorator fixed the tests I broke with adding the filter added test to verify the filter is called for the Github Graphql wrote test for IssueFilterRunner. Added test for TypeExclusionFilter and SeverityExclusionFilter Added tests for TypeComparator Added tests for SeverityComparator Added default comparators for IssueFilterRunner for real build.
I have reimplemented the change based on master if someone is interested ... |
@mc1arke I'm still buliding my own version of your project containing for example this feature and would like to try again to add it to the master. |
Describe the Enhancement
Filtering by severity which issues are added to MR
Additional context
Because it is not possible to disable many rules on sonar we put the ones we don't want to level info and don't want them to be as comment on the MR.
The text was updated successfully, but these errors were encountered: