-
Notifications
You must be signed in to change notification settings - Fork 351
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
Fixed alerts stay in Open state #1223
Comments
I suspect that renaming the workflow is the cause of the problem. Looking at the event log at the bottom of the alert page I see:
An alert is only considered fixed, if it has disappeared from all analysis configurations (aka categories). The workflow file name is part of the configuration key, so changing it causes problems like this. The easiest way to validate if this is indeed the problem would be to copy Of course you'd want to get rid of the duplicated |
Looks like you were correct, your solution worked as expected on the first try, super!👍 |
Happy I could help! Before deleting
to make it drop results from all files. I'm not sure what the behaviour is if there are no |
Actual behavior
I hacked out a small script to fix missing overrides alerts (this one if anyone's interested, but not relevant to this issue). After pushing the changes directly to the default branch (master, which is the only branch), the alerts are recognized as "fixed on master", but still appear as "open" (for example this alert).
Expected behavior
When alerts are fixed on the default branch, they appear as "closed".
Additional info
I read a similar issue, but in my case, the CodeQL config always had
name: "CodeQL"
. I did change the file name from codeql-analysis.yml to codeql.yml to match how the Github Action auto-generates the file, but as far as I remember the problem with being stuck in "open" already appeared before.The text was updated successfully, but these errors were encountered: