Issue Triage allows issue labelling #1029

Activity

1. github-actions commented on Apr 27, 2026

   

   github-actionsBot

   on Apr 27, 2026 – with GitHub Actions

   Contributor

   More actions

   1 related issue

   • [text-auditor] Fix misleading issue-triage labeling claims and one prompt typo #880 — it covers the same issue-triage labeling-claim mismatch in the read-only flow, includes prior investigation details, and links a PR that updated the read-only action/README; this may help determine whether this issue is a recurrence or a separate remaining gap.

   Note

   🔒 Integrity filter blocked 23 items

   The following items were blocked because they don't meet the GitHub integrity level.

   • #1029 issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #1029 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #1024 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #336 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #676 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #1025 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #684 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #875 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #132 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #139 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #1010 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #430 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #701 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #593 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #465 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #694 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • ... and 7 more items

   To allow these resources, lower min-integrity in your GitHub frontmatter:

   tools:
     github:
       min-integrity: approved  # merged | approved | unapproved | none

   ---

   What is this? | From workflow: Trigger Duplicate Issue Detector

   Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
2. github-actions commented on Apr 27, 2026

   

   github-actionsBot

   on Apr 27, 2026 – with GitHub Actions

   Contributor

   More actions

   tl;dr: issue-triage does not currently support applying labels; the capability was previously proposed in closed (unmerged) PR #434, so the best path is to reintroduce that change in a fresh PR (or reopen/cherry-pick #434) with current workflow/doc conventions.

   Recommendation
   Implement label support in Issue Triage as an allowlisted safe output (add-labels, max 3), and document it in both workflow docs. This appears to be a valid gap, not already shipped.

   Findings

   • Workflow source currently imports only comment safe output:
     • .github/workflows/gh-aw-issue-triage.md:13 → gh-aw-fragments/safe-output-add-comment-issue.md
     • .github/workflows/gh-aw-issue-triage.md:70-72 → no add-labels configuration
   • Published docs also list only comment safe output:
     • gh-agent-workflows/issue-triage/README.md:33-35
     • docs/workflows/gh-agent-workflows/issue-triage.md:31-33
   • Compiled lock prompt/tools confirm no label tool is exposed:
     • .github/workflows/gh-aw-issue-triage.lock.yml:235 → Tools: add_comment, missing_tool, missing_data, noop
     • .github/workflows/gh-aw-issue-triage.lock.yml:698 safe-output config contains add_comment but no add_labels
   • Prior implementation attempt exists but did not land:
     • PR #434 (“Add label, assignee, and reviewer capabilities to issue-triage and mention-in-issue workflows”) is closed and unmerged.

   Verification

   I ran targeted repository checks to verify current behavior:

   grep -nE "safe-output-add-comment-issue|safe-output-add-labels|safe-outputs:" .github/workflows/gh-aw-issue-triage.md

   Output:

   13:  - gh-aw-fragments/safe-output-add-comment-issue.md
   70:safe-outputs:
   

   grep -nE "^## Safe Outputs|add-comment|add-labels|assign-to-user" gh-agent-workflows/issue-triage/README.md

   Output:

   33:## Safe Outputs
   35:- `add-comment` — post a triage analysis comment on the issue
   

   grep -nE "add-labels:" .github/workflows/gh-aw-*.md

   Output:

   .github/workflows/gh-aw-dependency-review.md:78:  add-labels:
   .github/workflows/gh-aw-pr-labeler.md:61:  add-labels:
   .github/workflows/gh-aw-stale-issues-investigator.md:86:  add-labels:
   

   Detailed Action Plan

   1. Update .github/workflows/gh-aw-issue-triage.md to allow labeling safe output:
      • Add/inline label safe-output support (matching existing repo pattern).
      • Configure safe-outputs.add-labels with a conservative cap (max: 3) scoped to the triggering issue.
   2. Add a label allowlist input (recommended pattern from dependency-review):
      • Mirror the classification-labels + pre-sanitization approach from .github/workflows/gh-aw-dependency-review.md:43-47,77-129 so only explicitly allowed labels can be applied.
   3. Update the issue-triage prompt instructions in .github/workflows/gh-aw-issue-triage.md so agents apply labels only when evidence is clear and labels exist.
   4. Update docs to match behavior:
      • gh-agent-workflows/issue-triage/README.md
      • docs/workflows/gh-agent-workflows/issue-triage.md
   5. Recompile generated workflow:
      • Run make compile so .github/workflows/gh-aw-issue-triage.lock.yml reflects the new safe output/tool list.

   Related Items

   Type	Link	Relevance
   Issue	#1029	Current request: allow issue labeling in Issue Triage
   PR	#434	Prior implementation attempt for issue-triage labeling; closed unmerged
   Issue	#880	Related historical mismatch around labeling claims in legacy RO triage docs
   File	.github/workflows/gh-aw-issue-triage.md:13,70-72	Current workflow source lacks label safe output wiring
   File	gh-agent-workflows/issue-triage/README.md:33-35	Public docs currently advertise only add-comment
   File	.github/workflows/gh-aw-dependency-review.md:43-47,77-129	Existing allowlist/sanitization pattern to reuse for safe labels

   Note

   🔒 Integrity filter blocked 14 items

   The following items were blocked because they don't meet the GitHub integrity level.

   • #1029 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #1024 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #1025 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #694 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #676 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #139 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #1029 issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #697 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #608 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #937 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #589 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #430 issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #312 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #600 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

   To allow these resources, lower min-integrity in your GitHub frontmatter:

   tools:
     github:
       min-integrity: approved  # merged | approved | unapproved | none

   ---

   What is this? | From workflow: Trigger Issue Triage

   Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
3. fr4nc1sc0-r4m0n

   assigned

   Copilot

   and

   fr4nc1sc0-r4m0n

   on Apr 27, 2026
4. Copilot

   linked a pull request that will close this issueAdd classification-labels input and add-labels safe output to Issue Triage #1030on Apr 27, 2026
5. fr4nc1sc0-r4m0n

   closed this as completedin #1030on Apr 30, 2026