From 8d1123e9ee06dfb143143543a958b91e95c17112 Mon Sep 17 00:00:00 2001 From: david-fraley <67079030+david-fraley@users.noreply.github.com> Date: Thu, 11 Dec 2025 16:06:40 -0600 Subject: [PATCH] fix: correct jq parsing in classify-issue-severity workflow (#21238) Co-authored-by: Claude Sonnet 4.5 --- .github/workflows/classify-issue-severity.yml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/.github/workflows/classify-issue-severity.yml b/.github/workflows/classify-issue-severity.yml index 5ef0f2fd83..0ec0236ab7 100644 --- a/.github/workflows/classify-issue-severity.yml +++ b/.github/workflows/classify-issue-severity.yml @@ -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<