Conversation
Co-authored-by: RichardChen820 <99175581+RichardChen820@users.noreply.github.com>
.github/workflows/issue-triage.md
Outdated
| - priority-high | ||
| - priority-medium | ||
| - priority-low |
There was a problem hiding this comment.
@copilot, remove the content about the priority, determine the priority is a tricky part, let's focus on the triage per se first.
There was a problem hiding this comment.
Done — removed priority-high, priority-medium, and priority-low from the allowed labels list in e476424.
.github/workflows/issue-triage.md
Outdated
| ## Step 4: Assign Priority | ||
|
|
||
| Add exactly one priority label based on impact and severity: | ||
| - **priority-high**: Security vulnerabilities, data loss, service outages, issues blocking many users, or regressions in core functionality. | ||
| - **priority-medium**: Significant functionality issues or important feature requests with moderate impact. | ||
| - **priority-low**: Minor bugs, cosmetic issues, nice-to-have features, or low-impact requests. |
There was a problem hiding this comment.
@copilot, remove the content about the priority, determine the priority is a tricky part, let's focus on the triage per se first.
There was a problem hiding this comment.
Done — removed the "Assign Priority" step entirely in e476424. The workflow now goes directly from classifying the issue type to evaluating clarity.
.github/workflows/issue-triage.md
Outdated
| ## Step 6: Assign to Team Members | ||
|
|
||
| Assign the issue to an appropriate team member using these criteria: | ||
| - Use the GitHub API to search recent issues and PRs to identify active contributors and maintainers. | ||
| - For **bug** or **priority-high** issues, look for a maintainer who has recently closed similar bug reports or reviewed related PRs. | ||
| - For **feature-request** or **enhancement** issues, look for a contributor who has recently worked on related features. | ||
| - For **question** or **documentation** issues, assign to whoever most recently engaged with similar topics. | ||
| - If no suitable assignee can be identified from the repository history, leave the issue unassigned. | ||
|
|
||
| Do not invent usernames. Only assign to GitHub users who appear as active contributors in the repository's issue and PR history. |
There was a problem hiding this comment.
@copilot Remove the Assign to Team Members section, there's not much context abou feature owner in this repo, determine the owner is tricky for now, let's focus on the issue triage first
There was a problem hiding this comment.
Done — removed the "Assign to Team Members" section in e476424.
Co-authored-by: RichardChen820 <99175581+RichardChen820@users.noreply.github.com>
|
Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details. Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
Adds a GitHub Agentic Workflow (gh-aw) that automatically triages newly opened issues: classifying type, detecting duplicates, and requesting missing info when the description is unclear.
Workflow:
issue-triageTrigger:
issues: openedSteps (in order):
duplicate+ comment + stopbug/enhancement/feature-request/question/documentationneeds-more-info+ targeted clarifying comment if description is insufficientSafe outputs used:
add-labels,add-comment,update-issue— main job runs withissues: readonly; write operations delegated to separate safe-output jobs.Network: restricted to
api.github.com.Files
.github/workflows/issue-triage.md— workflow definition (editable at runtime without recompilation).github/workflows/issue-triage.lock.yml— compiled GitHub Actions YAML (generated, do not edit).gitattributes— marks lock files aslinguist-generated💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.