| name: 'Qwen Scheduled Issue Triage' |
|
|
| on: |
| schedule: |
| - cron: '0 * * * *' |
| workflow_dispatch: |
|
|
| concurrency: |
| group: '${{ github.workflow }}' |
| cancel-in-progress: true |
|
|
| defaults: |
| run: |
| shell: 'bash' |
|
|
| permissions: |
| contents: 'read' |
| id-token: 'write' |
| issues: 'write' |
| statuses: 'write' |
| packages: 'read' |
|
|
| jobs: |
| triage-issues: |
| timeout-minutes: 10 |
| if: |- |
| ${{ github.repository == 'QwenLM/qwen-code' }} |
| runs-on: 'ubuntu-latest' |
| permissions: |
| contents: 'read' |
| id-token: 'write' |
| issues: 'write' |
| steps: |
| - name: 'Find untriaged issues' |
| id: 'find_issues' |
| env: |
| GITHUB_TOKEN: '${{ secrets.GITHUB_TOKEN }}' |
| GITHUB_REPOSITORY: '${{ github.repository }}' |
| run: |- |
| echo "🔍 Finding issues without labels..." |
| NO_LABEL_ISSUES=$(gh issue list --repo ${{ github.repository }} --search "is:open is:issue no:label" --json number,title,body) |
| |
| echo '🔍 Finding issues without labels...' |
| NO_LABEL_ISSUES="$(gh issue list --repo "${GITHUB_REPOSITORY}" \ |
| --search 'is:open is:issue no:label' --json number,title,body)" |
|
|
| echo '🏷️ Finding issues that need triage...' |
| NEED_TRIAGE_ISSUES="$(gh issue list --repo "${GITHUB_REPOSITORY}" \ |
| --search 'is:open is:issue label:"status/needs-triage"' --json number,title,body)" |
|
|
| echo '🔄 Merging and deduplicating issues...' |
| ISSUES="$(echo "${NO_LABEL_ISSUES}" "${NEED_TRIAGE_ISSUES}" | jq -c -s 'add | unique_by(.number)')" |
|
|
| echo '📝 Setting output for GitHub Actions...' |
| echo "issues_to_triage=${ISSUES}" >> "${GITHUB_OUTPUT}" |
|
|
| - name: 'Run Qwen Issue Triage' |
| if: |- |
| ${{ steps.find_issues.outputs.issues_to_triage != '[]' }} |
| uses: 'QwenLM/qwen-code-action@5fd6818d04d64e87d255ee4d5f77995e32fbf4c2' |
| env: |
| GITHUB_TOKEN: '${{ secrets.GITHUB_TOKEN }}' |
| ISSUES_TO_TRIAGE: '${{ steps.find_issues.outputs.issues_to_triage }}' |
| REPOSITORY: '${{ github.repository }}' |
| with: |
| OPENAI_API_KEY: '${{ secrets.OPENAI_API_KEY }}' |
| OPENAI_BASE_URL: '${{ secrets.OPENAI_BASE_URL }}' |
| OPENAI_MODEL: '${{ secrets.OPENAI_MODEL }}' |
| settings_json: |- |
| { |
| "maxSessionTurns": 25, |
| "coreTools": [ |
| "run_shell_command(echo)", |
| "run_shell_command(gh label list)", |
| "run_shell_command(gh issue edit)", |
| "run_shell_command(gh issue view)", |
| "run_shell_command(gh issue list)" |
| ], |
| "sandbox": false |
| } |
| prompt: |- |
| ## Role |
| |
| You are an issue triage assistant. Analyze issues and apply |
| appropriate labels. Use the available tools to gather information; |
| do not ask for information to be provided. |
|
|
| |
|
|
| 1. Run: `gh label list --repo ${{ github.repository }} --limit 100` to get all available labels. |
| 2. Use shell command `echo` to check environment variable for issues to triage: $ISSUES_TO_TRIAGE (JSON array of issues) |
| 3. Review the issue title, body and any comments provided in the environment variables. |
| 4. Ignore any existing priorities or tags on the issue. |
| 5. Select the most relevant labels from the existing labels, focusing on kind/*, area/*, sub-area/* and priority/*. |
| 6. Get the list of labels already on the issue using `gh issue view ISSUE_NUMBER --repo ${{ github.repository }} --json labels -t '{{range .labels}}{{.name}}{{"\n"}}{{end}}' |
| 7. For area/* and kind/* limit yourself to only the single most applicable label in each case. |
| 8. Give me a single short paragraph about why you are selecting each label in the process. use the format Issue ID: , Title, Label applied:, Label removed, ovearll explanation |
| 9. Parse the JSON array from step 2 and for EACH INDIVIDUAL issue, apply appropriate labels using separate commands: |
| - `gh issue edit ISSUE_NUMBER --repo ${{ github.repository }} --add-label "label1"` |
| - `gh issue edit ISSUE_NUMBER --repo ${{ github.repository }} --add-label "label2"` |
| - Continue for each label separately |
| - IMPORTANT: Label each issue individually, one command per issue, one label at a time if needed. |
| - Make sure after you apply labels there is only one area/* and one kind/* label per issue. |
| - To do this look for labels found in step 6 that no longer apply remove them one at a time using |
| - `gh issue edit ISSUE_NUMBER --repo ${{ github.repository }} --remove-label "label-name1"` |
| - `gh issue edit ISSUE_NUMBER --repo ${{ github.repository }} --remove-label "label-name2"` |
| - IMPORTANT: Remove each label one at a time, one command per issue if needed. |
| 10. For each issue please check if CLI version is present, this is usually in the output of the /about command and will look like 0.1.5 |
| - Anything more than 6 versions older than the most recent should add the status/need-retesting label |
| 11. If you see that the issue doesn't look like it has sufficient information recommend the status/need-information label |
| - After applying appropriate labels to an issue, remove the "status/need-triage" label if present: `gh issue edit ISSUE_NUMBER --repo ${{ github.repository }} --remove-label "status/need-triage"` |
| - Execute one `gh issue edit` command per issue, wait for success before proceeding to the next |
| Process each issue sequentially and confirm each labeling operation before moving to the next issue. |
|
|
| |
|
|
| - Only use labels that already exist in the repository. |
| - Do not add comments or modify the issue content. |
| - Do not remove labels titled help wanted or good first issue. |
| - Triage only the current issue. |
| - Apply only one area/ label |
| - Apply only one kind/ label (Do not apply kind/duplicate or kind/parent-issue) |
| - Apply all applicable sub-area/* and priority/* labels based on the issue content. It's ok to have multiple of these. |
| - Once you categorize the issue if it needs information bump down the priority by 1 eg.. a p0 would become a p1 a p1 would become a p2. P2 and P3 can stay as is in this scenario. |
| Categorization Guidelines: |
| P0: Critical / Blocker |
| - A P0 bug is a catastrophic failure that demands immediate attention. It represents a complete showstopper for a significant portion of users or for the development process itself. |
| Impact: |
| - Blocks development or testing for the entire team. |
| - Major security vulnerability that could compromise user data or system integrity. |
| - Causes data loss or corruption with no workaround. |
| - Crashes the application or makes a core feature completely unusable for all or most users in a production environment. Will it cause severe quality degration? |
| - Is it preventing contributors from contributing to the repository or is it a release blocker? |
| Qualifier: Is the main function of the software broken? |
| Example: The gemini auth login command fails with an unrecoverable error, preventing any user from authenticating and using the rest of the CLI. |
| P1: High |
| - A P1 bug is a serious issue that significantly degrades the user experience or impacts a core feature. While not a complete blocker, it's a major problem that needs a fast resolution. |
| - Feature requests are almost never P1. |
| Impact: |
| - A core feature is broken or behaving incorrectly for a large number of users or large number of use cases. |
| - Review the bug details and comments to try figure out if this issue affects a large set of use cases or if it's a narrow set of use cases. |
| - Severe performance degradation making the application frustratingly slow. |
| - No straightforward workaround exists, or the workaround is difficult and non-obvious. |
| Qualifier: Is a key feature unusable or giving very wrong results? |
| Example: The gemini -p "..." command consistently returns a malformed JSON response or an empty result, making the CLI's primary generation feature unreliable. |
| P2: Medium |
| - A P2 bug is a moderately impactful issue. It's a noticeable problem but doesn't prevent the use of the software's main functionality. |
| Impact: |
| - Affects a non-critical feature or a smaller, specific subset of users. |
| - An inconvenient but functional workaround is available and easy to execute. |
| - Noticeable UI/UX problems that don't break functionality but look unprofessional (e.g., elements are misaligned or overlapping). |
| Qualifier: Is it an annoying but non-blocking problem? |
| Example: An error message is unclear or contains a typo, causing user confusion but not halting their workflow. |
| P3: Low |
| - A P3 bug is a minor, low-impact issue that is trivial or cosmetic. It has little to no effect on the overall functionality of the application. |
| Impact: |
| - Minor cosmetic issues like color inconsistencies, typos in documentation, or slight alignment problems on a non-critical page. |
| - An edge-case bug that is very difficult to reproduce and affects a tiny fraction of users. |
| Qualifier: Is it a "nice-to-fix" issue? |
| Example: Spelling mistakes etc. |
| Additional Context: |
| - If users are talking about issues where the model gets downgraded from pro to flash then i want you to categorize that as a performance issue |
| - This product is designed to use different models eg.. using pro, downgrading to flash etc. |
| - When users report that they dont expect the model to change those would be categorized as feature requests. |
| Definition of Areas |
| area/ux: |
| - Issues concerning user-facing elements like command usability, interactive features, help docs, and perceived performance. |
| - I am seeing my screen flicker when using Gemini CLI |
| - I am seeing the output malformed |
| - Theme changes aren't taking effect |
| - My keyboard inputs arent' being recognzied |
| area/platform: |
| - Issues related to installation, packaging, OS compatibility (Windows, macOS, Linux), and the underlying CLI framework. |
| area/background: Issues related to long-running background tasks, daemons, and autonomous or proactive agent features. |
| area/models: |
| - i am not getting a response that is reasonable or expected. this can include things like |
| - I am calling a tool and the tool is not performing as expected. |
| - i am expecting a tool to be called and it is not getting called , |
| - Including experience when using |
| - built-in tools (e.g., web search, code interpreter, read file, writefile, etc..), |
| - Function calling issues should be under this area |
| - i am getting responses from the model that are malformed. |
| - Issues concerning Gemini quality of response and inference, |
| - Issues talking about unnecessary token consumption. |
| - Issues talking about Model getting stuck in a loop be watchful as this could be the root cause for issues that otherwise seem like model performance issues. |
| - Memory compression |
| - unexpected responses, |
| - poor quality of generated code |
| area/tools: |
| - These are primarily issues related to Model Context Protocol |
| - These are issues that mention MCP support |
| - feature requests asking for support for new tools. |
| area/core: |
| - Issues with fundamental components like command parsing, configuration management, session state, and the main API client logic. Introducing multi-modality |
| area/contribution: |
| - Issues related to improving the developer contribution experience, such as CI/CD pipelines, build scripts, and test automation infrastructure. |
| area/authentication: |
| - Issues related to user identity, login flows, API key handling, credential storage, and access token management, unable to sign in selecting wrong authentication path etc.. |
| area/security-privacy: |
| - Issues concerning vulnerability patching, dependency security, data sanitization, privacy controls, and preventing unauthorized data access. |
| area/extensibility: |
| - Issues related to the plugin system, extension APIs, or making the CLI's functionality available in other applications, github actions, ide support etc.. |
| area/performance: |
| - Issues focused on model performance |
| - Issues with running out of capacity, |
| - 429 errors etc.. |
| - could also pertain to latency, |
| - other general software performance like, memory usage, CPU consumption, and algorithmic efficiency. |
| - Switching models from one to the other unexpectedly. |
|
|
