Hi, I’ve an automation setup to get triggered when there is a new PR comment on linked PRs. Automation works as a PR healer where it is expected to act on comment based on comment’s nature. But I’ve tested it on two repo ( 1 private, 1 public) but it is not getting triggered when I make a comment. I am author of these test PRs but I’ve added trigger rules for “comments by anyone” so expecting that it should get triggered on author’s comment as well.
Steps to Reproduce
Create an automation with “Comment added” trigger and choose options as per your setup.
Expected Behavior
Automation should get triggered on every comment matching trigger
Hey, thanks for the report. A couple of questions to narrow this down:
Is this automation set to Personal or Team scope? You can check this in the automation settings. If it’s Personal scope and you’re on a team plan, there’s a known issue where the webhook routing doesn’t match personal scope automations correctly. Switching to Team scope may fix it.
Are you leaving general PR conversation comments or inline review comments on specific lines in the diff? Right now only general conversation comments trigger automations. Inline review comments don’t.
Can you confirm the repos are connected through your team’s GitHub App installation in Cursor settings?
If switching to Team scope resolves it, that confirms the bug. Let me know how it goes.
It is set for “Team visible” if that is what you mean by team scope.
I am leaving inline review comments
Yes.
I think it is happening because of inline review comments. I tested by leaving general PR conversation comments and automation got triggered.
Do we know if we’ll get support of the inline-review-comment support? We’re building a PR-Healer automation to act on instructional review comments and respond on conversational review comments. Having more triggers can certainly help build more versatile automation.
One more query, this automation is also expected to act on any failed checks like linters.
To get the list of failed checks for the PR, it first used this command,
gh api repos/repo-name/check-runs
which returned
{"message":"Resource not accessible by integration","documentation_url":"https://docs.github.com/rest/checks/runs#list-check-runs-for-a-git-reference","status":"403"}gh: Resource not accessible by integration (HTTP 403)
And then try this command
gh pr checks pr-number
which returned
GraphQL: Resource not accessible by integration (node.statusCheckRollup.nodes.0.commit.statusCheckRollup)
but then it found a work around to fetch checks-logs via Github Action Run API.
gh api repos/repo-name/actions/runs --method GET -f branch=branch-name -f per_page=5
I’ll update my instructions to directly use Github Action Run API so that it doesn’t get stuck on auth issues but is there a way that other commands that automation was trying, could work? Is it the access issue on what cursor can do on our company’s github? OR is it what our company’s github has allowed like disabling CLI access?
Glad we sorted it out. Yeah, right now automations only trigger on general PR conversation comments, inline review comments on specific diff lines aren’t supported yet.
I get that this is critical for the PR healer use case, since inline review comments are the main way users interact there. I’ve passed this to the team as a feature request.
