Skip to content

Commit 10539b5

Browse files
authored
Improving the issue auto-labeling (#750)
Clarifying that adding tests should not be labeled as a Test Plan area. Always adding Needs Review label. ## GitHub issue number none ## **Associated Risks** still manually triggered ## ✅ **PR Checklist** - [x] **I have read the [contribution guidelines](https://github.com/microsoft/azure-devops-mcp/blob/main/CONTRIBUTING.md)** - [x] **I have read the [code of conduct guidelines](https://github.com/microsoft/azure-devops-mcp/blob/main/CODE_OF_CONDUCT.md)** - [x] Title of the pull request is clear and informative. - [x] 👌 Code hygiene - [x] 🔭 Telemetry added, updated, or N/A - [x] 📄 Documentation added, updated, or N/A - [x] 🛡️ Automated tests added, or N/A ## 🧪 **How did you test it?**
1 parent 30b3103 commit 10539b5

File tree

2 files changed

+8
-4
lines changed

2 files changed

+8
-4
lines changed

.github/ai-automation/ai-issue-processing-system-prompt.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,4 +68,8 @@ The `labels` array should contain strings representing the recommended label nam
6868
- Do not make assumptions beyond what is clearly stated or strongly implied
6969
- Ensure all recommended labels are meaningful and actionable
7070
- If uncertain about a label, exclude it rather than guessing
71-
- An issue may have multiple type labels and multiple area labels if appropriate
71+
72+
## [📌] Additional Guidelines
73+
74+
- Issues may warrant multiple type labels and/or multiple area labels when clearly justified by the content
75+
- **Test Plans Label Usage**: Only apply `Test Plans 🧪` when the issue directly relates to test management features, test case authoring, test suites, or the Test Plans API itself—not merely because testing or writing tests is mentioned as part of standard development practice

.github/workflows/ai-issue-processing.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -39,9 +39,9 @@ jobs:
3939
# Parse the JSON response to extract labels
4040
LABELS=$(echo "$AI_RESPONSE" | python3 -c "import sys, json; print(' '.join([f'--add-label \"{label}\"' for label in json.load(sys.stdin)['labels']]))")
4141
42-
# Add the recommended labels and remove the ai-issue-processing label
42+
# Add the recommended labels, always add "Needs Review 👓", and remove the ai-issue-processing label
4343
if [ -n "$LABELS" ]; then
44-
eval gh issue edit $ISSUE_NUMBER $LABELS --remove-label "ai-issue-processing" --repo ${{ github.repository }}
44+
eval gh issue edit $ISSUE_NUMBER $LABELS --add-label "Needs Review 👓" --remove-label "ai-issue-processing" --repo ${{ github.repository }}
4545
else
46-
gh issue edit $ISSUE_NUMBER --remove-label "ai-issue-processing" --repo ${{ github.repository }}
46+
gh issue edit $ISSUE_NUMBER --add-label "Needs Review 👓" --remove-label "ai-issue-processing" --repo ${{ github.repository }}
4747
fi

0 commit comments

Comments
 (0)