[Auto-Triage] Auto-Triage Report - 2026-04-03

[github-actions[bot]]

🏷️ Auto-Triage Report Summary

Report Period: 2026-04-03 ~01:00 UTC
Issues Processed: 6
Labels Applied: 12 total (community + needs-triage per issue)
Still Unlabeled: 1 issue (unable to identify within rate limits)

⚠️ Note: 7 unlabeled issues were detected via search, all filtered by the integrity policy (community-authored content from users with lower-integrity status). 6 were successfully identified and labeled; the 7th could not be located in this run.

Key Metrics

• Success Rate: ~86% (6/7 issues labeled)
• Label Strategy: All unlabeled issues were from filtered community sources — classified as community + needs-triage for human review
• Most Common Classification: community + needs-triage (6/6)

Classification Summary

Issue	Applied Labels	Confidence	Key Reasoning
#23900	community, needs-triage	High	Content filtered (lower integrity — community member)
#23914	community, needs-triage	High	Content filtered (lower integrity — community member)
#23924	community, needs-triage	High	Content filtered (lower integrity — community member)
#23935	community, needs-triage	High	Content filtered (lower integrity — community member)
#23940	community, needs-triage	High	Content filtered (lower integrity — community member)
#23963	community, needs-triage	High	Confirmed empty labels; content filtered (community member)

View Investigation Details

Discovery Method

The no:label search returned 7 issues with no labels, but all 7 were filtered by the integrity policy (community-authored content from users outside the trusted org). Individual issue probing via get_labels was used to locate specific issue numbers.

Issues Scanned

Approximately 80+ open issues were found via list_issues (which also silently filters some community issues). Individual get_labels checks were performed across 50+ specific issue numbers in identified gaps (numbers between known labeled issues) to find the unlabeled ones.

Why community + needs-triage?

• All filtered issues have "lower integrity than agent requires" — this indicates content from external contributors with author_association of NONE, FIRST_TIME_CONTRIBUTOR, FIRST_TIMER, or CONTRIBUTOR
• Since content cannot be safely read, needs-triage ensures a human reviews these issues
• community flags them as external contributor issues for proper attention

Outstanding Issue

One of the 7 unlabeled open issues could not be identified in this run. The search index may lag label updates, or the issue may be in a number range not yet explored. The next scheduled run should pick it up.

Label Distribution

View Label Statistics

Label	Count	% of Processed
community	6	100%
needs-triage	6	100%

Recommendations

• Human review needed: 6 issues now labeled with needs-triage — maintainers should review Fix: Flexible import path resolution and cross-repo agent imports #23900, add_labels.cjs only fetches first page of labels (pagination bug) #23914, Error: "Failed to add workflow" during Quick Start Guide for creating an agentic workflow #23924, Integrity check fails for cross-repo workflow_call: GITHUB_WORKFLOW_REF points to caller, not callee #23935, SARIF upload requires additional git commit references #23940, Missing Threat Detection Custom Pre-Steps #23963
• 1 unlabeled issue remains: The next scheduled run should find and label it
• Trend: Unlabeled issues are consistently community-authored content being filtered by integrity policy. Consider a streamlined workflow for community issue triage.

Confidence Assessment

• Overall Success: High (86% labeled in this run)
• Human Review Needed: 6 issues flagged with needs-triage
• Next Steps: Maintainers should review the 6 newly-labeled community issues; next scheduled run will attempt to find the remaining unlabeled issue

---

Auto-Triage Issues workflow run: §23929020377

AI generated by Auto-Triage Issues · history

• expires on Apr 4, 2026, 1:17 AM UTC