Update documentation to reflect org-level secrets #3
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| name: Issue Triage | ||
| on: | ||
| workflow_call: | ||
| secrets: | ||
| CLAUDE_CODE_OAUTH_TOKEN: | ||
| required: true | ||
| # Note: This secret is configured at the organization level and automatically | ||
| # inherited when using 'secrets: inherit' in the calling workflow | ||
| GITHUB_TOKEN: | ||
| required: true | ||
| # Note: This is automatically provided by GitHub Actions | ||
| # The following trigger is commented out since this is a reusable workflow. | ||
| # Uncomment it if you want to use this workflow directly in this repository. | ||
| # issues: | ||
| # types: [opened] | ||
| jobs: | ||
| triage-issue: | ||
| runs-on: ubuntu-latest | ||
| timeout-minutes: 10 | ||
| permissions: | ||
| contents: read | ||
| issues: write | ||
| steps: | ||
| - name: Checkout repository | ||
| uses: actions/checkout@v4 | ||
| with: | ||
| fetch-depth: 0 | ||
| - name: Triage issue with Claude | ||
| uses: anthropics/claude-code-action@v1 | ||
| with: | ||
| prompt: | | ||
| You're an issue triage assistant for GitHub issues. Your task is to analyze the issue and select appropriate labels from the provided list. | ||
| IMPORTANT: Don't post any comments or messages to the issue. Your only action should be to apply labels. | ||
| Issue Information: | ||
| - REPO: ${{ github.repository }} | ||
| - ISSUE_NUMBER: ${{ github.event.issue.number }} | ||
| TASK OVERVIEW: | ||
| 1. First, fetch the list of labels available in this repository by running: `gh label list`. Run exactly this command with nothing else. | ||
| 2. Next, use the GitHub tools to get context about the issue: | ||
| - You have access to these tools: | ||
| - mcp__github__get_issue: Use this to retrieve the current issue's details including title, description, and existing labels | ||
| - mcp__github__get_issue_comments: Use this to read any discussion or additional context provided in the comments | ||
| - mcp__github__update_issue: Use this to apply labels to the issue (do not use this for commenting) | ||
| - mcp__github__search_issues: Use this to find similar issues that might provide context for proper categorization and to identify potential duplicate issues | ||
| - mcp__github__list_issues: Use this to understand patterns in how other issues are labeled | ||
| - Start by using mcp__github__get_issue to get the issue details | ||
| 3. Analyze the issue content, considering: | ||
| - The issue title and description | ||
| - The type of issue (bug report, feature request, question, etc.) | ||
| - Technical areas mentioned | ||
| - Severity or priority indicators | ||
| - User impact | ||
| - Components affected | ||
| 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) | ||
| - 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. | ||
| 5. Apply the selected labels: | ||
| - Use mcp__github__update_issue to apply your selected labels | ||
| - DO NOT post any comments explaining your decision | ||
| - DO NOT communicate directly with users | ||
| - If no labels are clearly applicable, do not apply any labels | ||
| IMPORTANT GUIDELINES: | ||
| - Be thorough in your analysis | ||
| - Only select labels from the provided list above | ||
| - DO NOT post any comments to the issue | ||
| - Your ONLY action should be to apply labels using mcp__github__update_issue | ||
| - It's okay to not add any labels if none are clearly applicable | ||
| claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }} | ||
| github_token: ${{ secrets.GITHUB_TOKEN }} | ||
| claude_args: | | ||
| --allowedTools "Bash(gh label list),mcp__github__get_issue,mcp__github__get_issue_comments,mcp__github__update_issue,mcp__github__search_issues,mcp__github__list_issues" | ||
