From f4374cce125eda183fca9e23c86708d147f073a8 Mon Sep 17 00:00:00 2001 From: Muhammad Tahir Nawaz Date: Thu, 18 Jun 2026 16:09:02 +0500 Subject: [PATCH] ci: print Trivy fs findings to the workflow log The Trivy fs scan wrote its findings table to trivy-results.txt via the output option. That file was previously consumed by a 'comment results on the PR' step, which has since been removed, so the findings now go nowhere: a failing scan shows only 'exit code 1' in the logs with no detail. Drop the output redirect so the findings table prints to the Actions log, making failures self-explanatory. --- .github/workflows/trivy-go-tests.yaml | 1 - 1 file changed, 1 deletion(-) diff --git a/.github/workflows/trivy-go-tests.yaml b/.github/workflows/trivy-go-tests.yaml index 4e8df9f..5bd2022 100644 --- a/.github/workflows/trivy-go-tests.yaml +++ b/.github/workflows/trivy-go-tests.yaml @@ -65,7 +65,6 @@ jobs: scan-type: 'fs' ignore-unfixed: true format: 'table' - output: 'trivy-results.txt' severity: 'CRITICAL,HIGH,MEDIUM,LOW' exit-code: '1'