The issue-triage agentic workflow previously triggered on every new/reopened issue. This creates N workflow runs per day and provides immediate but resource-inefficient triage. By running once per day, we'll only use 1 premium request per month. In addition, this workflow won't run into permission issues where the issue can't trigger issues created by non-maintainers.

Changes

Trigger configuration (.github/workflows/issue-triage.md)

• Replaced issues: [opened, reopened] with schedule: cron: '0 0 * * *'
• Added workflow_dispatch for manual execution

Workflow logic

• Agent now uses list_issues with since parameter to fetch issues from last 24 hours
• Processes each issue sequentially with existing triage logic (labels, comments, analysis)
• Duplicate detection: Actively searches for duplicate and related issues using search_issues tool with key terms from issue title and description
• Related issues listing: Adds "🔗 Potentially Related Issues" section in triage comments with links to similar open and closed issues
• Handles empty result set gracefully

Concurrency

• Changed from gh-aw-${{ github.workflow }}-${{ github.event.issue.number }} to gh-aw-${{ github.workflow }}
• Ensures single daily run instead of concurrent per-issue runs

Compiled artifacts

Regenerated .github/workflows/issue-triage.lock.yml via gh-aw compile

Behavioral change

Issues triaged once daily (00:00 UTC) instead of immediately upon creation. Maximum triage delay: 24 hours. Use workflow_dispatch for immediate triage needs.

> [!WARNING]
>
>

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