Skip to content

Commit 5673ded

Browse files
labudisCopilot
andcommitted
Remove issue fields references (not supported yet)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1 parent 5691336 commit 5673ded

2 files changed

Lines changed: 4 additions & 10 deletions

File tree

docs/issue-triage.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
55
**Automatically triage issues when they are created or reopened**
66

7-
The [Issue Triage workflow](../workflows/issue-triage.md?plain=1) runs when issues are created or reopened to analyze content, check related items, set issue type and fields, add labels, detect duplicates, and post structured triage reports.
7+
The [Issue Triage workflow](../workflows/issue-triage.md?plain=1) runs when issues are created or reopened to analyze content, check related items, set issue type, add labels, detect duplicates, and post structured triage reports.
88

99
## Installation
1010

@@ -24,7 +24,7 @@ This walks you through adding the workflow to your repository.
2424
graph LR
2525
A[Issue Created/Reopened] --> B[Gather Context]
2626
B --> C[Spam & Quality Check]
27-
C --> D[Triage: Type, Labels, Fields]
27+
C --> D[Triage: Type, Labels]
2828
D --> E[Detect Duplicates]
2929
E --> F[Post Triage Report]
3030
```

workflows/issue-triage.md

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
description: |
33
Intelligent issue triage assistant that processes new and reopened issues.
44
Analyzes issue content, detects spam and incomplete reports, selects appropriate
5-
labels, sets issue type and fields, detects duplicates, and provides structured
5+
labels, sets issue type, detects duplicates, and provides structured
66
triage reports with debugging strategies and resource links. Helps maintainers
77
quickly understand and prioritize incoming issues.
88
@@ -89,13 +89,7 @@ If the issue has sufficient detail, proceed to Step 3.
8989
- If no labels are clearly applicable, do not apply any.
9090
- It is better to under-label than to speculatively add labels.
9191

92-
### 3c: Set issue fields
93-
94-
- If the issue already has a value set for a field, do not overwrite it.
95-
- Only set fields when you can confidently determine the value from the issue content.
96-
- Do not make up field values.
97-
98-
### 3d: Detect duplicates and related issues
92+
### 3c: Detect duplicates and related issues
9993

10094
- Review the similar issues found in Step 1.
10195
- Classify matches as:

0 commit comments

Comments
 (0)