Skip to content

ci: Use GITHUB_OUTPUT envvar instead of set-output command #4

ci: Use GITHUB_OUTPUT envvar instead of set-output command

ci: Use GITHUB_OUTPUT envvar instead of set-output command #4

Triggered via push July 10, 2024 23:57
Status Failure
Total duration 17s
Artifacts

win-build.yml

on: push
trufflehog-git-secrets-scan
3s
trufflehog-git-secrets-scan
build-windows64_coverage
0s
build-windows64_coverage
build-windows32
0s
build-windows32
build-windows64
0s
build-windows64
comment_PR_coverage
0s
comment_PR_coverage
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
trufflehog-git-secrets-scan
BASE and HEAD commits are the same. TruffleHog won't scan anything. Please see documentation (https://github.com/trufflesecurity/trufflehog#octocat-trufflehog-github-action).
trufflehog-git-secrets-scan
Process completed with exit code 1.
trufflehog-git-secrets-scan
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/