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

[github-actions[bot]]

🏷️ Auto-Triage Report Summary

Report Period: 2026-03-24 06:46 UTC (Scheduled Run)
Issues Processed: 0
Labels Applied: 0
Run: §23476748150

---

Key Metrics

• Success Rate: N/A — no actionable issues found
• Issues Fetched: 50 open issues (visible)
• Already Labeled: 50/50 (100%)
• Unlabeled (integrity-filtered): 6 issues blocked by DIFC policy

---

Classification Summary

No issues required labeling in this run. All 50 visible open issues already have at least one label applied.

Integrity Policy Impact

The no:label search returned 6 items that were removed by integrity policy (DIFC filter). These are issues from lower-integrity sources (community members without approved status) that this workflow cannot read or label.

This is a known limitation: the auto-triage workflow operates with min-integrity: approved, which restricts access to issues from unapproved contributors — precisely the community issues most likely to be unlabeled.

Recommendation: Consider lowering min-integrity to unapproved or none in the workflow frontmatter to allow labeling community-submitted issues:

tools:
  github:
    min-integrity: none

This would enable the auto-triage workflow to label the unlabeled community issues and better achieve the goal of reducing unlabeled issue percentage below 5%.

---

Label Distribution (Visible Issues)

View Label Statistics

All 50 visible issues are already labeled. Common labels observed:

• automation — most frequent (smoke tests, scheduled reports, CI agents)
• testing — smoke test reports
• agentic-workflows — workflow failure issues
• documentation + report — daily status reports
• performance — performance regression issues
• code-quality + refactoring — automated analysis issues
• safe-outputs + conformance — conformance checker issues
• dependencies — dependency update issues
• workflow-health — workflow health tracking

---

Recommendations

1. Lower min-integrity in the auto-triage workflow to none or unapproved to enable labeling of community-submitted issues — this is the primary blocker preventing progress toward the <5% unlabeled goal.
2. All currently-visible issues are well-labeled; no cleanup needed for the approved-integrity tier.
3. Consider scheduling more frequent runs once integrity is lowered to catch new community issues faster.

---

Confidence Assessment

• Overall Success: N/A (no issues to label)
• Human Review Needed: 6 issues are unlabeled but integrity-filtered
• Next Steps: Update workflow min-integrity setting to enable community issue triage

References:

• §23476748150

AI generated by Auto-Triage Issues · history

• expires on Mar 25, 2026, 6:51 AM UTC

[github-actions[bot]]

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

A newer discussion is available at Discussion #22681.