rickub/clipublic Fork
⑂ main
Commits
⬇ Clone ▾
git clone https://git.rickub.com/rickub/cli.git
git clone ssh://git@rickub.com/rickub/cli.git

Host key fingerprint (ed25519): SHA256:iycHnxEyq0Q7uyVpB7JlznP0G7JrTPXLYRcAU5CSLhc — verify it before your first connect.

Download ZIP
failure

Security #30

pull_request · rickub:feat/7-edit-title-and-body · 0e5a9421ran in 19s
queued <1s ran 19s total 19s
1 jobs
1 failed
19s duration
— tests
0 artifacts
failurevet / vuln / gosec / staticcheck / modules → Module integrity View log
Step failed A step exited non-zero. Open the log for the failing command's output.
vet / vuln / gosec / staticcheck / modules
failurevet / vuln / gosec / staticcheck / modules 19s

Annotations

  • ERROR go.mod/go.sum are not tidy; run 'go mod tidy' and commit
successCheckout <1s
successSet up Go 16s
successgo vet <1s
failureModule integrity <1s
skippedgovulncheck
skippedgosec
skippedstaticcheck
skippedRelease binary is reproducible from a clean tree

No test reports for this run.

Tell a job where its test runner writes its report and this tab fills in: how many tests passed, failed and were skipped, a bar of the result at a glance, then every failure first — with the assertion that failed and the output around it — over a per-suite list of cases and their durations. No scrolling a log for the word FAIL.

It is one reports: key on the job — a job key, not a step, so the report is collected whatever the job concluded. JUnit XML and go test -json are both understood, and most runners already emit one of them. reports: is a rickub extension and works only in .rickub/workflows/; in .github/workflows/ it is a parse error on purpose, because those files are also meant to run on github.com.