Post the per-image Grype scan table to Slack on PR and weekly runs - #175
Merged
Merged
Conversation
…n with no findings Adds an always_post input to the grype-report action. When true, the Slack message carries one status line per scanned image (clean, findings by severity, or scan did not complete), so a quiet run still proves its scans ran. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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
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.
Description
Follow-up to #174. A clean run posted nothing to Slack, so there was no way to tell a clean run from a run that never happened. PR validation and the weekly scan now always post the per-image table.
always_postinput on thegrype-reportaction (defaultfalse). Whentrue, the Slack message includes one status line per scanned image:✅ No findings,⚠️ N findings (by severity), or❌ scan did not complete. With findings, the table appears above the vulnerability list.container-validation.yml(PR runs) andscheduled-grype-scan.yml(weekly). The publish-time report keeps the findings-only behaviour.grype-scan-summary.shgains aSUMMARY_FORMAT=slackmode;grype-slack-digest.shaccepts an optionalSUMMARYand emits a payload even with no findings when it is set. WithoutSUMMARYit still emits nothing on a clean run.set -u, so a run where no scan produced a report still posts the all-❌ table instead of failing.Release Notes
N/A (CI only).
Testing
jq.create_new_tag.ymlnote); YAML parses.Notes for reviewers
Every PR run will now post one message to the channel, including from later pushes to the same PR. Fork PRs skip the post (no secret).