You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FEAT: AI-powered issue triage with GitHub Models (#477)
### Work Item / Issue Reference
<!--
IMPORTANT: Please follow the PR template guidelines below.
For mssql-python maintainers: Insert your ADO Work Item ID below
For external contributors: Insert Github Issue number below
Only one reference is required - either GitHub issue OR ADO Work Item.
-->
<!-- mssql-python maintainers: ADO Work Item -->
>
[AB#43191](https://sqlclientdrivers.visualstudio.com/c6d89619-62de-46a0-8b46-70b92a84d85e/_workitems/edit/43191)
-------------------------------------------------------------------
### Summary
Adds an automated GitHub Actions workflow that uses AI (GitHub Models -
GPT-4.1) to classify and analyze new issues, then sends formatted
notifications to a Teams channel.
**Changes:**
- Add `issue-triage.yml` workflow β AI-powered issue classification and
code-grounded analysis triggered on new issues or via manual dispatch
- Add `issue-notify.yml` workflow β Formats triage results into rich
HTML and posts to Teams via webhook
- Add `test-triage-local.js` β Local test script that mirrors the
workflow logic for development
- Update `.gitignore` β Exclude triage test output files
**Key capabilities:**
- Classifies issues into one of four categories: BUG, BREAK_FIX,
FEATURE_REQUEST, or DISCUSSION
- Fetches actual source files before AI analysis for code-grounded
accuracy
- For BUG/BREAK_FIX: provides verdict, root cause, evidence, recommended
fixes, and code locations
- For FEATURE_REQUEST/DISCUSSION: provides engineer guidance with
technical assessment, implementation approach, effort estimate, and
risks
- Verdict labels: Confirmed Bug, Likely Bug, Require More Analysis, Not
a Bug
- Uses GitHub Models API (gpt-4.1) with GITHUB_TOKEN β no Azure secrets
needed
- Teams notifications with bold labels, structured sections, and proper
HTML rendering
- HTML escaping on all untrusted/user-supplied values to prevent markup
injection
---------
Co-authored-by: Jahnvi Thakkar <61936179+jahnvi480@users.noreply.github.com>
0 commit comments