Skip to content

Auto-Triage: deterministically classify machine-generated aggregate reports #47373

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
pelikhan merged 2 commits into from
Jul 22, 2026
+11 −1
Merged

Auto-Triage: deterministically classify machine-generated aggregate reports #47373

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1c2a993
Initial plan
Copilot Jul 22, 2026
8472138
Add deterministic machine-generated aggregate report rule to auto-triage
Copilot Jul 22, 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
2 changes: 1 addition & 1 deletion .github/workflows/auto-triage-issues.lock.yml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

10 changes: 10 additions & 0 deletions .github/workflows/auto-triage-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -193,6 +193,16 @@ This label identifies issues opened by external community members and read-only
- `dependencies` - Mentions dependency updates, version bumps, package management
- `refactoring` - Discusses code restructuring without behavior changes

### Machine-Generated Aggregate Reports (deterministic, apply immediately)

These patterns identify machine-generated aggregate report issues. Apply only `report` and **do not** apply `needs-triage`:

- 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`
- Footer contains `> Generated by` or `> AI generated by`

When an issue matches any of the patterns above, apply only `report` and skip all other classification rules for that issue.

### Known Automation Title Patterns (high-confidence, apply immediately)

These title patterns identify machine-generated operational issues. Apply `automation` without further analysis and **do not** apply `needs-triage`:
Expand Down