`pull_request_review_comment` event causes prepare step to crash with "undefined is not an object (evaluating 'context.payload.comment.body')"

[leoarry]

Describe the bug
When the workflow is triggered by a pull_request_review_comment event, the prepare step crashes with:

undefined is not an object (evaluating 'context.payload.comment.body')

The action attempts to read the comment body to check for the trigger phrase (@claude), but context.payload.comment appears to be undefined for this event type on Gitea, causing an unhandled error that aborts the entire job.

To Reproduce

1. Configure the workflow to trigger on pull_request_review_comment
2. Open a pull request and add an inline review comment containing @claude
3. Observe the Actions run triggered by the event
4. See the prepare step fail with undefined is not an object (evaluating 'context.payload.comment.body')

Expected behavior
The action should either handle the pull_request_review_comment event correctly by reading the comment body from the appropriate payload field, or fail gracefully (e.g. skip with no trigger found) rather than throwing an unhandled exception.

Screenshots
N/A

Workflow yml file
N/A

API Provider

• Anthropic First-Party API (default)
• AWS Bedrock
• GCP Vertex

Additional context
This was reproduced on a self-hosted Gitea instance using markwylde/claude-code-gitea-action@v1.0.20. Gitea's pull_request_review_comment event payload may differ from GitHub's — the comment body may be nested under a different key (e.g. context.payload.review.body) rather than context.payload.comment.body.

Workaround: use issue_comment as the trigger event instead, and post @claude in a regular PR comment rather than an inline review comment.

[markwylde]

Thanks for the report @leoarry

Did you work out how to fix this? I don't have a lot of time to look into it myself.

[leoarry]

@markwylde yeah I put together a fix for this (is on my fork for this repo). Instead of crashing, it now works correctly and posts Claude's response to the main PR discussion.
I still have a tiny issue, inline review comment threading isn't fully solved yet, replies will go to the main PR discussion rather than inline to the review comment. I think this is due to some limitations in gitea webhook response but still need to investigate it properly.
Happy to look into it and open a PR once I get some spare time if that's ok with you.

[markwylde]

That would be amazing @leoarry. I'd really appreciate the help 👍

[leoarry]

@markwylde I've opened PR #19 to address this issue. Unfortunately it doesn't fix the inline comment behaviour, but it does prevent the crash and ensures responses are posted to the main PR conversation instead.
To also handle inline review comments I attempted a workaround by fetching the review comment data directly from Gitea, since it isn't included in the webhook payload. However there is currently no Gitea API endpoint for replying to an existing review comment; the functionality has been merged into main but didn't make it into 1.26.0. It may land in 1.27.0.

[markwylde]

Thanks a lot @leoarry. Yeah even if it doesn't fix the inline comment, this is better if it stops the crashing and gives some information in the pr.

[markwylde]

Released in v1.0.21