We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I've dismissed a few alerts in the security/code scanning alerts page.
But whenever the scan action is executed it detects these vulnerabilities as being new and fails the check under Code scanning results
Code scanning results
The job has the following permissions:
permissions: security-events: write
And I'm running the scan action like this:
- name: Scan image id: scan uses: anchore/scan-action@v3 with: image: ${{ steps.meta.outputs.tags }} fail-build: false severity-cutoff: "critical" acs-report-enable: true
Any ideas on why it's reporting the dismissed (and already existing) alerts as new in the pr checks?
The text was updated successfully, but these errors were encountered:
@bryopsida currently scan action and the github alerts page are not connected
This could be a feature enhancement where we could get scan action to be aware of these alerts and their dismissal. Is that what you're requesting?
cc @kzantow
Sorry, something went wrong.
No branches or pull requests
I've dismissed a few alerts in the security/code scanning alerts page.
But whenever the scan action is executed it detects these vulnerabilities as being new and fails the check under
Code scanning results
The job has the following permissions:
And I'm running the scan action like this:
Any ideas on why it's reporting the dismissed (and already existing) alerts as new in the pr checks?
The text was updated successfully, but these errors were encountered: