Enable /agent agentic-workflows debug handling in Issue Triage workflow

[Copilot]

The issue triage agent workflow could not be triggered via the /agent ... command path for workflow debugging. This change wires the workflow to accept /agent agentic-workflows debug and gives the agent the minimal read access/tools required to inspect workflow failures.

• Trigger surface update

  • Added on.slash_command to the agentic workflow source so issue comments with /agent can invoke the workflow.
  • Scoped to issue_comment events.

• Workflow-debug capability enablement

  • Added permissions.actions: read so the agent can read workflow/job/run metadata.
  • Enabled tools.agentic-workflows.
  • Expanded GitHub MCP toolsets to include actions alongside existing issues/labels.

• Prompt behavior update

  • Added an explicit goal line instructing the agent to handle /agent agentic-workflows debug by summarizing recent workflow failures in a concise comment.

on:
  issues:
    types: [opened]
  slash_command:
    name: agent
    events: [issue_comment]

permissions:
  issues: read
  actions: read

tools:
  github:
    toolsets: [issues, labels, actions]
  agentic-workflows: true

---

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

[apollo-cla]

@Copilot: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/

[apollo-librarian]

✅ Docs preview has no changes

The preview was not built because there were no changes.

Build ID: db27c437d5f4d373671bb2b5
Build Logs: View logs

[Copilot]

Pull request overview

This pull request enables the Issue Triage agentic workflow to respond to /agent agentic-workflows debug commands for debugging workflow failures. The workflow source file (.md) has been updated to add a new trigger, read permissions for workflow actions, and tooling to inspect workflow metadata.

Changes:

• Added slash_command trigger to accept /agent commands in issue comments
• Added actions: read permission and actions toolset to enable workflow metadata inspection
• Updated agent prompt to handle workflow debugging requests

Comments suppressed due to low confidence (1)

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

• The workflow now has two distinct trigger paths (new issues and /agent agentic-workflows debug commands), but the "Triage process" section only describes the issue triage flow. Consider adding a separate section or conditional instructions to clarify the workflow behavior when triggered by the debug command. For example, you might want to add something like "When triggered by /agent agentic-workflows debug, skip the standard triage process and focus on workflow debugging instead."

## Triage process
1. Read the triggering issue title, body, and existing labels.
2. If a type label is already present, keep it and do not add another type label.
3. If no type label is present, choose the best fit based on the issue content and add it.
4. If the issue lacks required details (for example, a bug report missing reproduction steps or environment details), add a comment asking for the missing information.
5. If the issue is a question and can be answered quickly, provide a brief answer with a link to the docs at https://go.apollo.dev/r/docs.
6. Avoid unnecessary comments; only comment when you need more information or have a clear next step.

---

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

[Copilot]

The lock file .github/workflows/issue-triage.lock.yml needs to be regenerated to reflect these changes to the source file. According to line 18-19 of the lock file, you need to run gh aw compile after editing the .md file.

The current lock file still has:

• on.issues.types: [opened] only (missing the slash_command trigger)
• permissions: {} (missing actions: read)
• GITHUB_TOOLSETS: "issues,labels" (missing actions)
• The old frontmatter-hash

Without regenerating the lock file, the changes in this PR won't actually take effect.