fix: correct jq parsing in classify-issue-severity workflow #21238
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.
Summary
Fixes the jq parsing error in the
classify-issue-severity.ymlworkflow that was causing failures in the "Extract Result from Execution File" step.Problem
The
claude-code-actionoutputs an array of conversation messages (following the Anthropic API message format), but the workflow was attempting to access.resultas if it were an object property. This caused the error:Solution
Updated the extraction logic to properly parse the message array structure:
Changes
.github/workflows/classify-issue-severity.ymlline 155jq -r '.result // empty'jq -r '.[].content[]? | select(.type == "text") | .text' | tail -n 1Test Plan
This fix addresses the error in workflow run: https://github.com/coder/coder/actions/runs/20148520999/job/57835360033
The workflow should now correctly:
🤖 Generated with Claude Code