Let the nightly scan fail instead of swallowing the exit code - #7
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe nightly vulnerability scan workflow now runs ChangesVulnerability scan workflow
Estimated code review effort: 1 (Trivial) | ~3 minutes Merge Risk: ⚪ Minimal · up to The workflow now propagates vulnerability-scan failures and removes redundant issue creation and permissions; no actionable merge-blocking risk remains after normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.) ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
govulncheck exits 3 on a finding, but the pipe into tee returned tee's status, and github's default shell has no pipefail, so the run stayed green. Last night's scan found five reachable stdlib issues and reported success.
cb32b2d to
6bd30b6
Compare
govulncheck exits 3 on a finding, but piping it into tee returned tee's status, and github's default shell is
bash -ewithout pipefail, so the run stayed green.Last night's scan did find the five reachable stdlib issues from go1.26.6 and reported success, no issue filed.
The pipe is gone, govulncheck writes to the log anyway. The issue creation is gone too, it had no dedupe so it would have opened one issue per night for as long as an advisory stands. A failed scheduled run notifies whoever last touched the cron, which is enough.
issues: writedropped with it.Summary by CodeRabbit