Repository navigation
fix(action): report pass/total-events when no audit data is found - #6
Merged
Merged
Conversation
The action's outputs read only from the `verify` step, which is skipped when no events file is found. The `verify-fallback` step wrote pass=false / total-events=0 for that case, but nothing read them, so the outputs came back empty and the "No audit data" test failed. Each output now falls back to the `verify-fallback` value. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
What was wrong
The action's
pass,total-events,chained-eventsandverify-jsonoutputs read only from theverifystep. That step is skipped when no events file is found. Theverify-fallbackstep writespass=false/total-events=0for that case, but no output read them, so the outputs came back empty. That's why the "Test: No audit data" job failed on the v0.6.13 push (and on 12 May).Fix
Each output now falls back to the
verify-fallbackvalue:steps.verify.outputs.X || steps.verify-fallback.outputs.X. Only one of the two steps runs, so the other side is always empty.The
fail-on-errorgate is unchanged.🤖 Generated with Claude Code