-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Fix first instance rule being used as rule description for all violations of that rule and other SARIF improvements #7640
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
base: main
Are you sure you want to change the base?
Conversation
… for all warnings for that rule
…n says it is, fix Error details: instance.runs[0].tool.driver.rules[3].defaultConfiguration.level is not one of enum values: none,note,warning,error
…date severity mapping, add more rule description mappings
Thanks for you contribution. I added a remark on how to keep this in sync for future changes. Possibly not something which should addressed before/in this PR. Also something like |
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.
Thanks for your contribution!!
I believe we'll need to rethink that getRuleDescription
somehow but unfortunately I don't see a quick/simple method..
@danmar I have simplified the approach significantly. I added genericMessage output for ErrorMessage class like you recommended and have reduced the regex to a minimum. I also removed the security violation list of errors and now I just add security tag if a CWE ID exists. |
Actually I just made a discovery. If I make all the descriptions for the rules blank strings, github will default to the instance specific description for each and this solves the problem. So this should greatly simplify the addition. |
…o the instance description
That is so much better 👍 Sounds like it will both simplify our job and make the user experience better. |
…ring so it doesnst produce trailing 0s
|
Before:

After:
