Skip to content
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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Conversation

justindbaur
Copy link
Member

@justindbaur justindbaur commented Feb 7, 2025

🎟️ Tracking

📔 Objective

Add <TreatWarningsAsErrors>true</TreatWarningsAsErrors> which means it should be a bad idea to merge to main 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 for Configuration=Release builds, not during normal development when you would run with Configuration=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 with dotnet build -c Release.

📸 Screenshots

⏰ Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Protected functional changes with optionality (feature flags)
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 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

Copy link

codecov bot commented Feb 7, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 44.30%. Comparing base (7e47e13) to head (3f83277).

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.
📢 Have feedback on the report? Share it here.

@withinfocus withinfocus changed the title Turn on TreatWarningsAsError for Release build Turn on TreatWarningsAsError Feb 7, 2025
Copy link

sonarqubecloud bot commented Feb 7, 2025

Copy link
Contributor

github-actions bot commented Feb 7, 2025

Logo
Checkmarx One – Scan Summary & Detailsac080e7b-265c-4422-8da0-9b1003bb6825

Great job, no security vulnerabilities found in this Pull Request

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Looks good to me.

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.

3 participants