You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm setting up a new CodeQL instance, looking at the alerts for the PR branch, I saw I had thousands:
Hundreds appeared to be in generated XAML files from the platform build process (probably something they should look at later, but unrelated to our codebase directly):
So, I added in the config file to ignore these files:
However, all the alerts for these files still remained open on the next pass of the CI, since these files are listed as ignored, it'd be nice to have them all automatically deleted/closed.
It makes it really hard to find the actual things I should be looking for. And it seems like I can only close 25 items at a time, page by page in the filtered view.
Probably going to have to close my PR and open a new PR just to get a clean list...
The text was updated successfully, but these errors were encountered:
Unfortunately, filtering files with paths and paths-ignore has no effect for compiled languages. For compiled languages such as C# CodeQL will analyze all files as "seen" by a compiler during the build.
I'm setting up a new CodeQL instance, looking at the alerts for the PR branch, I saw I had thousands:
Hundreds appeared to be in generated XAML files from the platform build process (probably something they should look at later, but unrelated to our codebase directly):
So, I added in the config file to ignore these files:
However, all the alerts for these files still remained open on the next pass of the CI, since these files are listed as ignored, it'd be nice to have them all automatically deleted/closed.
It makes it really hard to find the actual things I should be looking for. And it seems like I can only close 25 items at a time, page by page in the filtered view.
Probably going to have to close my PR and open a new PR just to get a clean list...
The text was updated successfully, but these errors were encountered: