Repository navigation
Conversation
When tia-report is set, the action also runs `cifail selection-misses` over the JUnit/TRX reports in `log`, adds a "Candidate selection misses" section to the step summary and PR comment, and exposes the count as the selection-misses output. With fail: true a miss fails the step. A check that cannot run (report missing or unusable, no test report in log, an image without the command) warns and says "Not checked", with the output left empty: never a silent "no miss", never a red step on its own. The report is mounted on its own, so a path outside the workspace works. The README documents the two-job workflow. Closes #46 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A plain run: step is bash -e without pipefail, so `if step | tee` tested tee's status and the miss-fails-the-step check could never pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner
Author
This was referenced Oct 25, 2026
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #46.
cifail selection-misses(#44, shipped in 0.4.0) was CLI-only. The action now takes atia-report: <path>input.What it does
tia-reportis set, the action runsselection-misses --json --tia <report> <log>in a seconddocker run, over the same reports as the analysis.argsbelongs to analyze/gate, so it is not passed on.dotnet tia explain.selection-misses, holds the count. It is empty when the check could not run.fail: true, a miss fails the step like any other negative result: exit 1 when the analysis itself passed.exit-codeis still the analysis's own code.loghas no JUnit/TRX, or the image is older than 0.4.0. Then the step prints a::warning::and the section says Not checked: , quoting cifail's own message. That is never a silent "no miss", and it never fails the step on its own.runner.tempor an absolutegithub.workspacepath works too.Docs
SebHenn/dotnet-tiawithreport:and uploads the report; the run onmainfinds the merged PR's run and downloads the report.Tests
docker-smoke's "Run the action's own step script" now also runs the script, as the runner does, withtia-reportset. The JUnit failure in that test matches a rule, so only the miss can fail the step:fail: true: the step fails, the section and the list item render,selection-misses=1andexit-code=0.selection-missesis empty and the step exits 0.There is no Docker on my machine, so I ran this whole CI step locally with real libjq and a fake
dockerthat runs the locally built CLI. All assertions passed, along with the other cases: no miss, unusable report, log-only input, andtia-reportunset.🤖 Generated with Claude Code