Skip to content

fix: correct jq parsing in classify-issue-severity workflow #21238

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
david-fraley merged 1 commit into from
Dec 11, 2025
+8 −2
Merged

fix: correct jq parsing in classify-issue-severity workflow #21238

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions .github/workflows/classify-issue-severity.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,8 +150,14 @@ jobs:
exit 1
fi

# Extract the result from the execution file
RESULT=$(jq -r '.result // empty' < "$EXECUTION_FILE")
# The execution file is an array of conversation messages
# Extract the last assistant message's text content
RESULT=$(jq -r '.[].content[]? | select(.type == "text") | .text' < "$EXECUTION_FILE" | tail -n 1)

if [ -z "$RESULT" ]; then
echo "No text content found in execution file"
exit 1
fi

{
echo "result<<EOF"
Expand Down
Loading