success
Release
queued 1s ran 3s total 4s
1 jobs
0 failed
4s duration
— tests
0 artifacts
build and publish ${{ github.ref_name }}
successbuild and publish ${{ github.ref_name }}
successSet up job
cloning bots-garden/mini-me-kit @ 3caf5757482e91db12eb4d143aef0110d0c7acdeaction softprops/action-gh-release@v2: node20 (_actions/softprops/action-gh-release/v2)
successCheckout <1s
(checkout already performed by the runner — delivered as the read-only work disk)
successRelease notes from the tag message 2s
Run
git fetch --force origin "refs/tags/${GITHUB_REF_NAME}:refs/tags/${GITHUB_REF_NAME}"
path="${RUNNER_TEMP}/notes.md"
git tag -l --format='%(contents)' "${GITHUB_REF_NAME}" > "${path}"
echo "path=${path}" >> "${GITHUB_OUTPUT}"
ciguest: network up (172.30.0.2/30 via 172.30.0.1)ciguest: starting dockerd (overlay2, data-root on scratch)ciguest: dockerd is readyciguest: loaded baked image postgres_16-alpine.tar.gz: Loaded image: postgres:16-alpineciguest: 1 baked image archive(s) loaded (no per-job registry pull needed)ciguest: logged into registry registry.rickub.com as rickub
successPublish the release <1s
👩🏭 Creating new GitHub release for tag v0.0.1...Finalizing release...Getting assets list...🎉 Release ready at https://rickub.com/bots-garden/mini-me-kit/releases/v0.0.1
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.