Restore deleted deviations suppression query#876
Merged
MichaelRFairhurst merged 11 commits intomainfrom Apr 22, 2025
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull Request Overview
This pull request restores the previously deleted DeviationsSuppression.ql query by adding a corresponding change note.
- Restores the DeviationsSuppression.ql query used for generating the Guideline Compliance Summary
- Adds a change note to document the restoration
Files not reviewed (4)
- cpp/common/src/codingstandards/cpp/deviations/DeviationsSuppression.qhelp: Language not supported
- cpp/common/src/codingstandards/cpp/deviations/DeviationsSuppression.ql: Language not supported
- cpp/common/test/deviations/deviations_report_deviated/DeviationsSuppression.expected: Language not supported
- cpp/common/test/deviations/deviations_report_deviated/DeviationsSuppression.qlref: Language not supported
Tip: If you use Visual Studio Code, you can request a review from Copilot before you push from the "Source Control" tab. Learn more
This is required for our reporting scripts. Changes implemented to support reporting of locations and messages for new deviation formats.
MichaelRFairhurst
requested changes
Apr 1, 2025
Collaborator
MichaelRFairhurst
left a comment
There was a problem hiding this comment.
Looks good, just some small points to bring up!
cpp/common/src/codingstandards/cpp/deviations/CodeIdentifierDeviation.qll
Outdated
Show resolved
Hide resolved
cpp/common/src/codingstandards/cpp/deviations/CodeIdentifierDeviation.qll
Show resolved
Hide resolved
cpp/common/src/codingstandards/cpp/deviations/CodeIdentifierDeviation.qll
Outdated
Show resolved
Hide resolved
The deviated locations now include the line with the _end marker, for any element before the marker.
Ensure begin/end column code works as expected
MichaelRFairhurst
approved these changes
Apr 21, 2025
Collaborator
MichaelRFairhurst
left a comment
There was a problem hiding this comment.
Good catch on the Attribute primary suppressed location logic!
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
I incorrectly deleted the
DeviationsSuppression.qlquery in #807. This query is still used as part of generating our Guideline Compliance Summary, and is useful for customers wanting to generate a SARIF file including suppression information.Change request type
.ql,.qll,.qlsor unit tests)Rules with added or modified queries
Release change checklist
A change note (development_handbook.md#change-notes) is required for any pull request which modifies:
If you are only adding new rule queries, a change note is not required.
Author: Is a change note required?
🚨🚨🚨
Reviewer: Confirm that format of shared queries (not the .qll file, the
.ql file that imports it) is valid by running them within VS Code.
Reviewer: Confirm that either a change note is not required or the change note is required and has been added.
Query development review checklist
For PRs that add new queries or modify existing queries, the following checklist should be completed by both the author and reviewer:
Author
As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.
Reviewer
As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.