From fd2c17f101639b10696381c1fd85fa735239090a Mon Sep 17 00:00:00 2001 From: Ashwin Bhat Date: Thu, 4 Sep 2025 20:58:52 -0700 Subject: [PATCH] feat: enhance issue triage workflow with priority labeling and OIDC support (#540) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Add id-token write permission for OIDC token exchange - Update prompt to emphasize adding P1/P2/P3 priority labels based on label descriptions - Ensure Claude selects appropriate priority labels from the available options 🤖 Generated with [Claude Code](https://claude.ai/code) Co-authored-by: Claude --- .github/workflows/issue-triage.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/issue-triage.yml b/.github/workflows/issue-triage.yml index 65cbc2f..c3ac7e0 100644 --- a/.github/workflows/issue-triage.yml +++ b/.github/workflows/issue-triage.yml @@ -11,6 +11,7 @@ jobs: permissions: contents: read issues: write + id-token: write steps: - name: Checkout repository @@ -78,7 +79,7 @@ jobs: 4. Select appropriate labels from the available labels list provided above: - Choose labels that accurately reflect the issue's nature - Be specific but comprehensive - - Select priority labels if you can determine urgency (high-priority, med-priority, or low-priority) + - IMPORTANT: Add a priority label (P1, P2, or P3) based on the label descriptions from gh label list - Consider platform labels (android, ios) if applicable - If you find similar issues using mcp__github__search_issues, consider using a "duplicate" label if appropriate. Only do so if the issue is a duplicate of another OPEN issue.