-
Notifications
You must be signed in to change notification settings - Fork 468
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
Test PR for #6367 #6375
Test PR for #6367 #6375
Conversation
Test PR for #6367
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #6375 +/- ##
=======================================
Coverage 96.10% 96.11%
=======================================
Files 1361 1361
Lines 316050 316050
Branches 10186 10186
=======================================
+ Hits 303752 303757 +5
+ Misses 9868 9865 -3
+ Partials 2430 2428 -2 |
@mavasani This is green :( |
Yes, will investigate why the analyzers are not executing |
@Youssef1313 The problem seems to be that we enable CAxxxx rules as warnings with the below: roslyn-analyzers/src/Directory.Build.props Lines 29 to 32 in 2b5a3b2
Due to this regression: #6245, CAxxxx rules are no longer being bulk escalated to warning/error. I am going to work on a PR to pull in the latest NetAnalyzers package in the repo to first fix this and also the new violations that come out of it. I am going to block your PR #6367 until this work is done. |
@Youssef1313 This also explains why #6339 had no new violations. |
Moving to latest pre-release NetAnalyzers package produces 410 CA warnings!! |
Closing in favor of #6380 |
Test PR for #6367