ops(security): scan main on push too, so post-fix scans clear stale alerts#163
Merged
Conversation
…lerts Same systemic fix as cycles-server. Trivy alerts on refs/heads/main only auto-close when a SARIF scan publishes against main itself; previously the workflow only ran on PRs, leaving stale alerts after every merge. Adds push:main trigger with same paths filter.
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
1 participant
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.
Same systemic fix as cycles-server. Adds
push: branches: [main]to pr-container-scan.yml so post-merge scans publish to the main-branch alert track (currently stale after every fix merge).