Skip to content

fix: improve issue-triage prompt robustness to prevent no-output failures #10504

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: improve issue-triage prompt robustness to prevent no-output failures #10504

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d447dd3
Initial plan
Copilot Apr 27, 2026
d4ac0ed
fix: improve issue-triage prompt robustness to prevent no-output fail…
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
8 changes: 6 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 @@ -48,7 +48,7 @@ You're a triage assistant for the TypeSpec GitHub repository. Your task is to an

## Available Labels

To find the available labels for this repository, read the file `eng/common/config/labels.ts` in the repository. This file contains all the label definitions organized by category:
To find the available labels for this repository, use the `get_file_contents` tool to read the file `eng/common/config/labels.ts` (owner: `microsoft`, repo: `typespec`). This file contains all the label definitions organized by category:

- **Area labels** (`AreaLabels`): Used to categorize which area of the codebase the issue belongs to (e.g. `compiler:core`, `emitter:openapi3`, `ide`, etc.). Always try to assign the most specific area label that matches.
- **Issue kind labels** (`issue_kinds`): Used to classify the type of issue (`bug`, `feature`, `docs`).
Expand Down Expand Up @@ -104,7 +104,7 @@ Only use labels defined in that file.
- Do NOT change the semantics of the reproduction

**Construct a playground link**: If the issue has reproduction TypeSpec code but no playground link, construct one using this URL format:
`https://typespec.io/playground?c={encoded}` where `{encoded}` is the repro code URL-encoded (percent-encoded). Use `web-fetch` to verify the playground link works by fetching it.
`https://typespec.io/playground?c={encoded}` where `{encoded}` is the repro code URL-encoded (percent-encoded). If the `web_fetch` tool is available, use it to verify the playground link works by fetching it.

Skip this step entirely for feature requests and documentation issues.

Expand Down Expand Up @@ -143,3 +143,7 @@ Only use labels defined in that file.
- Skip the reproduction block entirely for feature requests and docs issues
- Skip "Suggested next steps" if there's nothing actionable to suggest
- Do NOT include any text about agentic workflows, how to install them, or any self-promotional content. Do NOT mention AI, bots, or agents.

## Important

You MUST call at least one safe output tool (`add_comment`, `add_labels`, or `noop`) before finishing. If you encounter errors with any tool or cannot complete the triage, call `noop` with a message describing what went wrong.
Loading