diff --git a/packages/core/src/skills/builtin/github-issue-triage/references/triage_rules.md b/packages/core/src/skills/builtin/github-issue-triage/references/triage_rules.md index f6817d5dc0..dbdce0a784 100644 --- a/packages/core/src/skills/builtin/github-issue-triage/references/triage_rules.md +++ b/packages/core/src/skills/builtin/github-issue-triage/references/triage_rules.md @@ -34,7 +34,7 @@ If there is a cross-referenced PR in `cross_references` where `is_pr` is `true` - Assign the PR to the author: `gh pr edit --add-assignee ` - Assign the issue to the author: `gh issue edit --add-assignee ` - Add the help wanted label to the issue to prevent the bot from closing the PR again: `gh issue edit --add-label "help wanted"` - - Comment on the issue: `gh issue comment --body "@, apologies! It looks like your PR was incorrectly closed by our bot. I have reopened it and assigned this issue to you. Would you like to continue working on it?"` + - Comment on the issue: `gh issue comment --body "### Triage Summary\n\n\n\n@, apologies! It looks like your PR was incorrectly closed by our bot. I have reopened it and assigned this issue to you. Would you like to continue working on it?"` - Comment on the PR: `gh pr comment --body "@, apologies for the bot closing this PR! We have reopened it. Please sync your branch to the latest \`main\` and we will have someone review it shortly."` - Execute `gh issue edit --remove-label "status/need-triage"` - **STOP EXECUTION**. @@ -105,3 +105,5 @@ Review the issue comments to see if a community member has already identified th - If you categorized the issue as **Maintainer-only**, also run `gh issue edit --remove-label "status/need-triage" --add-label "🔒 maintainer only"`. - Action: `gh issue comment --body "### Triage Summary\n\n"` - **STOP EXECUTION**. + --body "### Triage Summary\n\n"` +- **STOP EXECUTION**.