diff --git a/.github/workflows/issue-triage.lock.yml b/.github/workflows/issue-triage.lock.yml index 5834f57..19f510b 100644 --- a/.github/workflows/issue-triage.lock.yml +++ b/.github/workflows/issue-triage.lock.yml @@ -21,7 +21,7 @@ # # For more information: https://github.github.com/gh-aw/introduction/overview/ # -# Triage new issues by labeling them by type and priority, identifying duplicates, asking clarifying questions when descriptions are unclear, and assigning them to the right team members. +# Triage new issues by labeling them by type, identifying duplicates, asking clarifying questions when descriptions are unclear, and assigning them to the right team members. # # gh-aw-metadata: {"schema_version":"v1","frontmatter_hash":"62cbec402b084d34edc9c5ede40bb98b504f9c621a0bd5e235f4f41516e1d394","compiler_version":"v0.50.4"} @@ -347,7 +347,7 @@ jobs: mkdir -p /tmp/gh-aw/safeoutputs mkdir -p /tmp/gh-aw/mcp-logs/safeoutputs cat > /opt/gh-aw/safeoutputs/config.json << 'GH_AW_SAFE_OUTPUTS_CONFIG_EOF' - {"add_comment":{"max":1},"add_labels":{"allowed":["bug","enhancement","question","documentation","duplicate","invalid","wontfix","help wanted","good first issue","priority/critical","priority/high","priority/medium","priority/low"],"max":3},"missing_data":{},"missing_tool":{},"noop":{"max":1},"update_issue":{"max":1}} + {"add_comment":{"max":1},"add_labels":{"allowed":["bug","enhancement","question","documentation","duplicate","invalid","wontfix","help wanted","good first issue"],"max":3},"missing_data":{},"missing_tool":{},"noop":{"max":1},"update_issue":{"max":1}} GH_AW_SAFE_OUTPUTS_CONFIG_EOF cat > /opt/gh-aw/safeoutputs/tools.json << 'GH_AW_SAFE_OUTPUTS_TOOLS_EOF' [ @@ -373,7 +373,7 @@ jobs: "name": "add_comment" }, { - "description": "Add labels to an existing GitHub issue or pull request for categorization and filtering. Labels must already exist in the repository. For creating new issues with labels, use create_issue with the labels property instead. CONSTRAINTS: Maximum 3 label(s) can be added. Only these labels are allowed: [bug enhancement question documentation duplicate invalid wontfix help wanted good first issue priority/critical priority/high priority/medium priority/low].", + "description": "Add labels to an existing GitHub issue or pull request for categorization and filtering. Labels must already exist in the repository. For creating new issues with labels, use create_issue with the labels property instead. CONSTRAINTS: Maximum 3 label(s) can be added. Only these labels are allowed: [bug enhancement question documentation duplicate invalid wontfix help wanted good first issue].", "inputSchema": { "additionalProperties": false, "properties": { @@ -982,7 +982,7 @@ jobs: uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 env: WORKFLOW_NAME: "Issue Triage Workflow" - WORKFLOW_DESCRIPTION: "Triage new issues by labeling them by type and priority, identifying duplicates, asking clarifying questions when descriptions are unclear, and assigning them to the right team members." + WORKFLOW_DESCRIPTION: "Triage new issues by labeling them by type, identifying duplicates, asking clarifying questions when descriptions are unclear, and assigning them to the right team members." HAS_PATCH: ${{ steps.collect_output.outputs.has_patch }} with: script: | @@ -1198,7 +1198,7 @@ jobs: uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 env: GH_AW_AGENT_OUTPUT: ${{ env.GH_AW_AGENT_OUTPUT }} - GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG: "{\"add_comment\":{\"max\":1},\"add_labels\":{\"allowed\":[\"bug\",\"enhancement\",\"question\",\"documentation\",\"duplicate\",\"invalid\",\"wontfix\",\"help wanted\",\"good first issue\",\"priority/critical\",\"priority/high\",\"priority/medium\",\"priority/low\"],\"max\":3},\"missing_data\":{},\"missing_tool\":{},\"update_issue\":{\"allow_body\":true,\"max\":1}}" + GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG: "{\"add_comment\":{\"max\":1},\"add_labels\":{\"allowed\":[\"bug\",\"enhancement\",\"question\",\"documentation\",\"duplicate\",\"invalid\",\"wontfix\",\"help wanted\",\"good first issue\"],\"max\":3},\"missing_data\":{},\"missing_tool\":{},\"update_issue\":{\"allow_body\":true,\"max\":1}}" with: github-token: ${{ secrets.GH_AW_GITHUB_TOKEN || secrets.GITHUB_TOKEN }} script: | diff --git a/.github/workflows/issue-triage.md b/.github/workflows/issue-triage.md index 32d136c..e7660cc 100644 --- a/.github/workflows/issue-triage.md +++ b/.github/workflows/issue-triage.md @@ -1,5 +1,5 @@ --- -description: Triage new issues by labeling them by type and priority, identifying duplicates, asking clarifying questions when descriptions are unclear, and assigning them to the right team members. +description: Triage new issues by labeling them by type, identifying duplicates, asking clarifying questions when descriptions are unclear, and assigning them to the right team members. on: issues: types: [opened, reopened] @@ -34,10 +34,6 @@ safe-outputs: - wontfix - help wanted - good first issue - - priority/critical - - priority/high - - priority/medium - - priority/low max: 3 noop: --- @@ -60,23 +56,14 @@ Analyze the issue title and body and apply one of these labels: - **documentation** — Documentation is missing or incorrect - **invalid** — The issue is not actionable (e.g., spam, gibberish, unrelated) -### 2. Assess Priority - -Assign a priority label based on impact and urgency: - -- **priority/critical** — Data loss, security vulnerability, complete outage, or production blocker -- **priority/high** — Significant functionality broken, affects many users, no workaround -- **priority/medium** — Partial functionality impacted, workaround exists, affects some users -- **priority/low** — Minor issue, cosmetic, or rarely encountered edge case - -### 3. Check for Duplicates +### 2. Check for Duplicates Search existing open and recently closed issues for similar topics. If you find a likely duplicate: - Apply the **duplicate** label - Add a comment referencing the original issue (e.g., "This appears to be a duplicate of #123. Please follow that issue for updates.") -- Do NOT assign or set priority for duplicates +- Do NOT assign or set labels for duplicates -### 4. Request Clarification When Needed +### 3. Request Clarification When Needed If the issue lacks sufficient information to triage or reproduce, add a comment asking for clarification. Examples of missing information: - No steps to reproduce for a bug @@ -91,7 +78,7 @@ Ask focused, specific questions. Example comment: > - Steps to reproduce the issue > - Expected behavior and what you observed instead -### 5. Assign to Team Members +### 4. Assign to Team Members Assign the issue to appropriate team members based on these guidelines: