feat: trigger on issues opened when @cursor in title or body
Extend check-comment.sh to parse issues event payloads; document issue_comment + issues opened as supported workflow triggers. Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
@@ -27,6 +27,8 @@ name: Cursor Agent
|
||||
on:
|
||||
issue_comment:
|
||||
types: [created]
|
||||
issues:
|
||||
types: [opened]
|
||||
|
||||
jobs:
|
||||
cursor:
|
||||
@@ -70,7 +72,7 @@ For playground repos that commit directly to the default branch (no PR workflow)
|
||||
|
||||
## How it works
|
||||
|
||||
When someone mentions `@cursor` in a new issue or PR comment:
|
||||
When someone mentions `@cursor` in a new issue (title or body), a new issue/PR comment, or similar:
|
||||
|
||||
1. The action parses the webhook payload (`GITHUB_EVENT_PATH`) and checks for `@cursor`.
|
||||
2. Comments from the `cursor` user are ignored to prevent feedback loops.
|
||||
@@ -93,6 +95,7 @@ You can ask Cursor to review a PR, refine a feature request, or implement a chan
|
||||
|
||||
## Supported events
|
||||
|
||||
- `issue_comment` with `types: [created]` — issue and PR timeline comments (recommended)
|
||||
- `issue_comment` with `types: [created]` — issue and PR timeline comments
|
||||
- `issues` with `types: [opened]` — new issue if `@cursor` appears in title or body
|
||||
|
||||
`pull_request_review_comment` is not enabled by default: Gitea's payload uses a `review` object instead of `comment`, which is easy to get wrong. Open an issue if you need that trigger tested on your Gitea version.
|
||||
|
||||
Reference in New Issue
Block a user