Conversation
- Update `last-msg` text extraction to use `lastMsg.planGenerated.plan.steps` or `lastMsg.userFeedbackRequired.message` - Update `pr-url` to use `session.outputs[].pullRequest.url` fetched via `getSession(id)`
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
GreyC
left a comment
There was a problem hiding this comment.
LGTM. Both fixes match the confirmed API structure from live session data:
last-msg: correctly handles typed union fields (planGenerated.plan.steps,userFeedbackRequired.message) with JSON fallbackpr-url: correctly reads fromsession.outputs[].pullRequest.urlviagetSession()instead of searching activities
Verified against real API responses from sessions 2705438157339577511 and 5813762652404726973.
Fixes issue #9.
last-msgandpr-urlcommands inpackages/cli/src/index.tsparsed Jules activity fields that were guessed and never verified.last-msghas been updated to extract text properly fromlastMsg.planGenerated.plan.stepsorlastMsg.userFeedbackRequired.message.pr-urlhas been updated to usesession.outputs[].pullRequest.urlfetched viagetSession(id)instead of searching activities.PR created automatically by Jules for task 2705438157339577511 started by @GreyC