[Auto-Triage] Auto-Triage Report — 2026-04-02 #24034
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Auto-Triage Issues. A newer discussion is available at Discussion #24104. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Auto-Triage Report Summary
Report Period: 2026-04-02T06:53 UTC (on-demand backfill pass)
Issues Processed: 0
Labels Applied: 0
Still Unlabeled: 8 issues (integrity policy restriction)
Key Metrics
Classification Summary
No issues were labeled in this run. All 8 unlabeled issues were filtered by the workflow integrity policy because they were submitted by external community contributors (integrity level below
"approved").Why No Labels Were Applied
Integrity Policy Restriction — Details
The auto-triage agent uses a secure execution environment that enforces content integrity policies to prevent prompt injection attacks. Issues submitted by community members who are external to the organization (
NONE,FIRST_TIME_CONTRIBUTOR,FIRST_TIMER,CONTRIBUTORassociation) are classified as low-integrity content.When the agent attempted to read and classify unlabeled issues, all 8 were blocked with:
This is a security feature, not a bug — it prevents malicious issue content from manipulating the triage agent's behavior via prompt injection.
Impact
Recommendations
References:
Beta Was this translation helpful? Give feedback.
All reactions