Closed msnwatson closed 2 months ago
109 tests ±0 109 :white_check_mark: ±0 33s :stopwatch: -1s 33 suites ±0 0 :zzz: ±0 33 files ±0 0 :x: ±0
Results for commit d310c8f9. ± Comparison against base commit f85cbb92.
:recycle: This comment has been updated with latest results.
Overall Project | 65.91% | :x: |
---|
There is no coverage information present for the Files changed
What was the problem?
We don't use the Postgres container in production any more but the publishing makes us continue to have SecRel scanning on it.
Associated tickets or Slack threads:
3008
How does this fix it?[^1]
Stop publishing postgres and scanning with SecRel
How to test this PR
[^1]: Pull-Requests guidelines. If PR is significant, update Current Software State wiki page. [^secrel]: To check if a PR will succeed in the SecRel workflow, test PRs in the SecRel pipeline.