build: Disable warnings in third-party code #1353
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We already disabled warnings-as-errors in third-party code, but this goes futher to completely disable third-party warnings. They are mostly noise, and distracting. If they aren't errors, we shouldn't have our build logs flooded with them.
cosmin
approved these changes
Feb 27, 2024
|
Thank you, I was about to suggest the same thing as I got tired of looking at random warnings in the build output. |
github-actions
bot
added
the
status: archived
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We already disabled warnings-as-errors in third-party code, but this goes futher to completely disable third-party warnings. They are mostly noise, and distracting. If they aren't errors, we shouldn't have our build logs flooded with them.