-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Turn on TreatWarningsAsError #5384
base: main
Are you sure you want to change the base?
Conversation
- Break Api intentionally
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5384 +/- ##
=======================================
Coverage 44.30% 44.30%
=======================================
Files 1497 1497
Lines 69207 69207
Branches 6241 6241
=======================================
Hits 30661 30661
Misses 37223 37223
Partials 1323 1323 ☔ View full report in Codecov by Sentry. |
|
Great job, no security vulnerabilities found in this Pull Request |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Looks good to me.
🎟️ Tracking
📔 Objective
Add
<TreatWarningsAsErrors>true</TreatWarningsAsErrors>
which means it should be a bad idea to merge tomain
with new warnings. I have temporarily excluded issues that exist today. It does technically allow new warnings of those types to get introduced but all new warnings types will block.NOTE: This only blocks warnings forConfiguration=Release
builds, not during normal development when you would run withConfiguration=Debug
this can be nice as it allows you to experiment and test your changes easier but it can also suck when the build works locally but fails in CI. Luckily it it pretty easy to recreate the CI behavior withdotnet build -c Release
.📸 Screenshots
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes