name: Qwen Automated Issue Triage on: issues: types: [opened, reopened] jobs: triage-issue: timeout-minutes: 5 if: ${{ github.repository == 'QwenLM/qwen-code' }} permissions: issues: write contents: read id-token: write concurrency: group: ${{ github.workflow }}-${{ github.event.issue.number }} cancel-in-progress: true runs-on: ubuntu-latest steps: - name: Run Qwen Issue Triage uses: QwenLM/qwen-code-action@5fd6818d04d64e87d255ee4d5f77995e32fbf4c2 env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} with: version: 0.0.4 OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }} settings_json: | { "coreTools": [ "run_shell_command(gh label list)", "run_shell_command(gh issue edit)", "run_shell_command(gh issue list)" ], "sandbox": false } prompt: | You are an issue triage assistant. Analyze the current GitHub issue and apply the most appropriate existing labels. Steps: 1. Run: `gh label list --repo ${{ github.repository }} --limit 100` to get all available labels. 2. Review the issue title and body provided in the environment variables. 3. Select the most relevant labels from the existing labels, focusing on kind/*, area/*, and priority/*. 4. Apply the selected labels to this issue using: `gh issue edit ${{ github.event.issue.number }} --repo ${{ github.repository }} --add-label "label1,label2"` 5. If the issue has a "status/need-triage" label, remove it after applying the appropriate labels: `gh issue edit ${{ github.event.issue.number }} --repo ${{ github.repository }} --remove-label "status/need-triage"` Guidelines: - Only use labels that already exist in the repository. - Do not add comments or modify the issue content. - Triage only the current issue. - Assign all applicable kind/*, area/*, and priority/* labels based on the issue content.