fix(auto-triage): add missing classification rules for unlabeled report-type issues - #49679
Merged
Merged
Conversation
…sues - Expand Machine-Generated Aggregate Reports examples to include [agentic-token-audit], [model-resolution], [copilot-cli-research], and a generic [<workflow-id>] placeholder - Generalize gh-aw-workflow-call-id tracker marker description to cover all workflows (not just deep-report) - Add [Parent] tracking issues to Known Automation Title Patterns table with automation label - Recompile auto-triage-issues.lock.yml to keep in sync Closes #49366 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix auto-triage classifier skipping certain report-type issues
fix(auto-triage): add missing classification rules for unlabeled report-type issues
Aug 1, 2026
pelikhan
marked this pull request as ready for review
August 2, 2026 00:17
Contributor
There was a problem hiding this comment.
Pull request overview
Expands Auto-Triage rules for recurring machine-generated issues and synchronizes the compiled workflow.
Changes:
- Adds report classifications for three workflow prefixes.
- Adds
[Parent]automation classification. - Broad catch-all currently risks misclassifying automation issues as reports.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/auto-triage-issues.md |
Expands classification rules. |
.github/workflows/auto-triage-issues.lock.yml |
Updates generated body metadata. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 1
- Review effort level: Balanced
|
|
||
| - Title indicates a generated aggregate report (for example starts with `[daily-report]`, `[deep-report]`, or contains `Daily Report`) | ||
| - Body contains a tracker marker like `gh-aw-workflow-call-id: github/gh-aw/deep-report` | ||
| - Title indicates a generated aggregate report — for example starts with a workflow-prefix tag like `[daily-report]`, `[deep-report]`, `[agentic-token-audit]`, `[model-resolution]`, `[copilot-cli-research]`, or any other `[<workflow-id>]` prefix, OR contains `Daily Report` |
Contributor
|
🎉 This pull request is included in a new release. Release: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Auto-Triage classifier was reporting 100% success while 11 issues remained unlabeled — the gap caused by missing rules for four recurring machine-generated issue patterns:
[agentic-token-audit],[model-resolution],[copilot-cli-research], and[Parent].Changes
[agentic-token-audit],[model-resolution],[copilot-cli-research], plus a generic[<workflow-id>]catch-all so future report workflows don't require another rule update; generalized thegh-aw-workflow-call-idtracker marker from thedeep-report-specific example to any workflow path[Parent]→automation; these Issue Arborist tracking issues lack a> Generated byfooter so they can't be caught by the aggregate-reports heuristic and need an explicit entry.lock.ymlrecompiled to stay in sync