Skip to content

Fix tool name references in issue-triage workflow prompt #10502

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
timotheeguerin merged 2 commits into from
Apr 27, 2026
Merged

Fix tool name references in issue-triage workflow prompt #10502

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
62a1571
Initial plan
Copilot Apr 27, 2026
4d0d578
fix: update tool name references in issue-triage.md to match actual M…
Copilot Apr 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/issue-triage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,10 +58,10 @@ Only use labels defined in that file.

## Instructions

1. Retrieve the issue content using the `get_issue` tool. If the issue is obviously spam, generated by a bot, or not an actual issue to be worked on, then add an issue comment with a one-sentence analysis and exit the workflow.
1. Retrieve the issue content using the `issue_read` tool (method: `get`). If the issue is obviously spam, generated by a bot, or not an actual issue to be worked on, then add an issue comment with a one-sentence analysis and exit the workflow.

2. Gather additional context about the issue:
- Fetch any comments on the issue using the `get_issue_comments` tool
- Fetch any comments on the issue using the `issue_read` tool (method: `get_comments`)

3. **Duplicate detection**: Search for existing issues that may cover the same problem.
- Extract 2-3 distinct keyword queries from the issue title and body (e.g., key error messages, feature names, affected components).
Expand Down
Loading