-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
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
gh-112301: Add Warning Count to Warning Check Tooling #122711
gh-112301: Add Warning Count to Warning Check Tooling #122711
Conversation
I have made the requested changes; please review again |
Thanks for making the requested changes! : please review the changes made to 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.
Handful of review comments for you, otherwise looking good! :)
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.
LGTM, thanks Nate! Really excited to see this land 🚀
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.
Reminder: you can commit these changes via the GitHub UI: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
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.
Thank you! 🚀
…22711) Co-authored-by: blurb-it[bot] <43283697+blurb-it[bot]@users.noreply.github.com> Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
This adds the feature of specifying how many warnings should be ignored in a particular file for the check compiler warning tooling. This makes adding a particular file to the warning ignore files a bit more tolerable because it means that changes that introduce more warnings to a file will be caught. If a warning is fixed by a change but a new warning is introduced this will not be caught, however. That would require maintaining a list of specific warnings to ignore, which would be a bit overkill.
This change also removes duplicate warnings from being processed by the tooling, so that the accurate number of warnings per file can be specified when ignoring warnings in the
.warningignore_*
file.