Fix issue-triage workflow to add labels via add-labels safe-output

[Copilot]

The issue-triage workflow claimed to add labels in comments but labels were never applied to issues.

Root Cause

Workflow configured update-issue safe-output, which only supports status/title/body updates—not labels.

Changes

• Added add-labels safe-output configuration with all 14 labels from the workflow prompt
• Set max: 10 and target: triggering to allow multiple labels per triggering issue
• Recompiled workflow to include add-labels handler in safe_outputs job

safe-outputs:
  add-labels:
    allowed: [bug, enhancement, question, documentation, sdk/dotnet, sdk/go, sdk/nodejs, sdk/python, priority/high, priority/low, testing, security, needs-info, duplicate]
    max: 10
    target: triggering

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/repos/github/copilot-sdk/labels
  • Triggering command: /usr/bin/curl curl -s -H Accept: application/vnd.github+json REDACTED (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

The issue triage didn't add labels, fix that

Custom agent used: debug-agentic-workflow
Debug and refine agentic workflows using gh-aw CLI tools - analyze logs, audit runs, and improve workflow performance

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull request overview

This PR fixes the issue triage workflow to enable label addition functionality by adding the add-labels safe-output configuration, which was missing from the original workflow setup.

Changes:

• Added add-labels safe-output configuration to the issue triage workflow with 14 allowed labels
• Updated compiled lock file to reflect the new safe-output configuration
• Enabled the AI agent to add labels to issues during triage

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
.github/workflows/issue-triage.md	Added add-labels safe-output configuration with allowed labels list and max/target settings
.github/workflows/issue-triage.lock.yml	Compiled workflow file reflecting the new add-labels configuration in multiple locations (config.json, tools.json, validation.json, and handler config)

Comments suppressed due to low confidence (1)

.github/workflows/issue-triage.md:15

• While the workflow-level permissions are correctly set (they don't need issues: write since the safe_outputs job handles that), it would be helpful to add a comment explaining why issues: write is not included here. This would prevent future confusion about how labels can be added without write permissions. Consider adding a comment like: # Note: issues:write not needed - handled by safe_outputs job.

permissions:
  contents: read
  issues: read
  pull-requests: read

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.