Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion .github/workflows/issue-triage.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,15 +4,20 @@ description: Triage new issues by labeling and requesting missing details.
on:
issues:
types: [opened]
slash_command:
name: agent
events: [issue_comment]
permissions:
issues: read
actions: read
roles: all
network:
allowed:
- "api.github.com"
tools:
github:
toolsets: [issues, labels]
toolsets: [issues, labels, actions]
agentic-workflows: true
Comment on lines +7 to +20
Copy link

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copilot uses AI. Check for mistakes.
safe-outputs:
add-labels:
allowed: ["bug 🐞", "feature 🎉", "question ❓", "docs 📝", "triage"]
Expand All @@ -31,6 +36,7 @@ You are a triage assistant for the apollographql/rover repository.
- Ensure each new issue has exactly one type label: **bug 🐞**, **feature 🎉**, **question ❓**, or **docs 📝**.
- Add the **triage** label if it is missing.
- Request missing information when it is needed to proceed.
- When triggered by `/agent agentic-workflows debug`, inspect recent workflow failures and provide a concise debugging summary comment.

## Triage process
1. Read the triggering issue title, body, and existing labels.
Expand Down
Loading