[Auto-Triage] Auto-Triage Report — 2026-03-31

[github-actions[bot]]

🏷️ Auto-Triage Report Summary

Report Period: 2026-03-31T06:54Z (Scheduled Run)
Issues Processed: 0
Labels Applied: 0
Still Unlabeled: 9 issues (blocked by integrity filter)

Key Metrics

• Success Rate: 0% (integrity policy prevented access to all unlabeled issues)
• Unlabeled Issues Found: 9 (via no:label search)
• Issues Filtered by Integrity Policy: 9

Classification Summary

No issues could be classified in this run. All 9 unlabeled open issues were filtered by the repository's integrity policy, which restricts reading content below the configured trust threshold.

Integrity Policy Limitation

The GitHub MCP integrity filter blocked all 9 unlabeled issues from being read. This typically occurs when issues were created by authors with NONE or FIRST_TIME_CONTRIBUTOR association and the workflow's min-integrity is set above unapproved.

To enable triage of these issues, the workflow frontmatter can be updated:

tools:
  github:
    min-integrity: unapproved  # Allow reading lower-trust issue content

⚠️ Note: Lowering min-integrity allows the agent to read potentially untrusted content. Prompt injection defenses should be reviewed before enabling this.

Recommendations

• Consider lowering min-integrity to unapproved for the auto-triage workflow so it can read and label community-submitted issues
• The 9 blocked unlabeled issues likely include community-submitted issues that most need the community + type labels applied
• Human reviewers may want to manually label these issues until the policy is adjusted

---

References:

• §23784474597

AI generated by Auto-Triage Issues · history

• expires on Apr 1, 2026, 6:57 AM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Auto-Triage Issues.

A newer discussion is available at Discussion #23704.