Support for `issue_comment` event (PR comment)

[adamamer20]

Hi!

I'm currently using presubmit/ai-reviewer for automated reviews on pull requests from first-time contributors. These PRs typically originate from forks, so the appropriate GitHub event to safely run workflows with necessary permissions is pull_request_target rather than pull_request.

However, when triggered with the pull_request_target event, the ai-reviewer action throws an unsupported event warning and skips execution:

Warning: Skipped: unsupported github event

Here's the relevant debug log:

##[debug]Starting: Run AI Reviewer
Run presubmit/ai-reviewer@latest
  with:
  env:
    GITHUB_TOKEN: ***
    LLM_API_KEY: ***
    LLM_MODEL: claude-3-7-sonnet-20250219
Warning: Skipped: unsupported github event
##[debug]Node Action run completed with exit code 0

Could you add support for handling the pull_request_target event? This would likely require minimal changes, as the payload is similar to pull_request, and it would significantly help projects relying on forks.

Thanks a lot!

[bstanga]

Hi! That pull_request_target event is already supported, see here. I also just tested that the fork from another repo works (see example)

If the issue is particular to first-time contributors, I recommend to double check your repo settings about their permissions. By default, Github prevents first-time contributors to run workflows on the main repo. Read more about this here

[adamamer20]

You're right, it works—sorry for the confusion! 😊

The workflow was actually triggered by another event (issue_comment: types: [created]). What I was aiming for is to have the workflow trigger when there’s either a pull_request_review_requested event or when a maintainer of the repo comments in the PR with /pr-ai-review.

Here's the current workflow file for context:
https://github.com/projectmesa/mesa-frames/blob/main/.github/workflows/presubmit.yml

Is this something that can be expected to work? Or is there a better way to directly trigger the ai-reviewer?
Thanks a lot for your help and for the great work on this project!

[bstanga]

Got it!

Yes, I think having an on-demand command to trigger a review makes sense. I'll add that in the coming days.

About pull_request_review_requested, would you prefer that both summarization and review happens only when the review is requested and not automatically? Would having a setting to switch between both make sense? Or how do you see this working for you?

[adamamer20]

About pull_request_review_requested, would you prefer that both summarization and review happens only when the review is requested and not automatically? Would having a setting to switch between both make sense? Or how do you see this working for you?

It's fine to have just the review, I think! The summary can already be handled by GitHub Copilot if needed. But the default works well as it is.
Thanks a lot for the support!