eslint-plugin-primer-react 0.0.0-20260722211726 → 0.0.0-20260723113417
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.gitattributes +1 -0
- package/.github/aw/actions-lock.json +9 -0
- package/.github/workflows/ci.yml +3 -3
- package/.github/workflows/issue-triage.lock.yml +1699 -0
- package/.github/workflows/issue-triage.md +107 -0
- package/.github/workflows/release.yml +3 -3
- package/CHANGELOG.md +1 -1
- package/package.json +1 -1
|
@@ -0,0 +1,107 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: |
|
|
3
|
+
Triage assistant for new and reopened issues in eslint-plugin-primer-react.
|
|
4
|
+
Reads the issue and its comments, classifies the issue type when it is unset,
|
|
5
|
+
applies existing relevant labels, checks for likely duplicate or related issues,
|
|
6
|
+
and asks the author for missing information only when it is genuinely needed.
|
|
7
|
+
Each action carries a rationale and a confidence level; low-confidence changes are
|
|
8
|
+
routed as suggestions for maintainer approval rather than applied silently.
|
|
9
|
+
|
|
10
|
+
on:
|
|
11
|
+
issues:
|
|
12
|
+
types: [opened, reopened]
|
|
13
|
+
reaction: eyes
|
|
14
|
+
|
|
15
|
+
permissions: read-all
|
|
16
|
+
|
|
17
|
+
network: defaults
|
|
18
|
+
|
|
19
|
+
safe-outputs:
|
|
20
|
+
set-issue-type:
|
|
21
|
+
allowed: [Bug, Feature, Task]
|
|
22
|
+
max: 1
|
|
23
|
+
target: triggering
|
|
24
|
+
add-labels:
|
|
25
|
+
allowed:
|
|
26
|
+
- bug
|
|
27
|
+
- documentation
|
|
28
|
+
- enhancement
|
|
29
|
+
- question
|
|
30
|
+
- duplicate
|
|
31
|
+
- good first issue
|
|
32
|
+
- help wanted
|
|
33
|
+
- invalid
|
|
34
|
+
- wontfix
|
|
35
|
+
- dependencies
|
|
36
|
+
- a11y eng
|
|
37
|
+
- waiting for author response
|
|
38
|
+
- "Severity-*"
|
|
39
|
+
- "size: *"
|
|
40
|
+
- "component: *"
|
|
41
|
+
blocked: ["~*", "*[bot]"]
|
|
42
|
+
max: 3
|
|
43
|
+
target: triggering
|
|
44
|
+
add-comment:
|
|
45
|
+
max: 1
|
|
46
|
+
|
|
47
|
+
tools:
|
|
48
|
+
github:
|
|
49
|
+
toolsets: [issues, labels]
|
|
50
|
+
min-integrity: none
|
|
51
|
+
|
|
52
|
+
timeout-minutes: 15
|
|
53
|
+
---
|
|
54
|
+
|
|
55
|
+
# Issue triage
|
|
56
|
+
|
|
57
|
+
You triage issue #${{ github.event.issue.number }} in this repository, an ESLint plugin
|
|
58
|
+
for Primer React components. Work only from what the issue and its comments actually say —
|
|
59
|
+
do not invent missing context or make assumptions the content does not support.
|
|
60
|
+
|
|
61
|
+
Attach a short **rationale** and a **confidence** level to every classification you make
|
|
62
|
+
(issue type and labels). When your confidence in a type or label is not high, route it as a
|
|
63
|
+
**suggestion** for a maintainer to approve rather than applying it. Keep visible output to a
|
|
64
|
+
minimum: do **not** post a routine triage report, and only comment when you actually need
|
|
65
|
+
something from the author.
|
|
66
|
+
|
|
67
|
+
## 1. Gather context
|
|
68
|
+
|
|
69
|
+
- Read the issue body and all of its comments.
|
|
70
|
+
- List the repository's existing labels and the available issue types.
|
|
71
|
+
- Search for similar existing issues to spot duplicates and related work.
|
|
72
|
+
|
|
73
|
+
## 2. Classify the issue type
|
|
74
|
+
|
|
75
|
+
- If the issue already has a type, leave it as-is.
|
|
76
|
+
- If it has none, set the single best-fitting type (`Bug`, `Feature`, or `Task`) with a
|
|
77
|
+
rationale. If it is genuinely ambiguous between very different categories, suggest the type
|
|
78
|
+
instead of applying it, or leave it unset.
|
|
79
|
+
|
|
80
|
+
## 3. Apply labels
|
|
81
|
+
|
|
82
|
+
- Add only labels that already exist in this repository and clearly apply, each with a
|
|
83
|
+
rationale. Fewer, accurate labels are better than speculative ones; if nothing clearly
|
|
84
|
+
applies, add none.
|
|
85
|
+
- The `react` label is already applied automatically — do not add it.
|
|
86
|
+
- Be careful: labels can drive downstream automation. When a label is a judgement call,
|
|
87
|
+
suggest it rather than applying it.
|
|
88
|
+
|
|
89
|
+
## 4. Duplicates and related issues
|
|
90
|
+
|
|
91
|
+
- If you find a high-confidence duplicate of an existing open issue, apply the `duplicate`
|
|
92
|
+
label with a rationale. Do **not** close the issue.
|
|
93
|
+
- You may note likely duplicate or related issue links in the missing-information comment
|
|
94
|
+
described below if you are already posting one. Otherwise stay silent.
|
|
95
|
+
|
|
96
|
+
## 5. Missing information
|
|
97
|
+
|
|
98
|
+
- If the issue lacks the detail needed to act on it (for a bug: reproduction steps, expected
|
|
99
|
+
vs. actual behavior, the failing rule, versions; for other types: the equivalent
|
|
100
|
+
specifics), post a single comment that politely asks the author for exactly what is missing
|
|
101
|
+
and why, and add the `waiting for author response` label. Do not ask for information the
|
|
102
|
+
issue already provides.
|
|
103
|
+
|
|
104
|
+
## 6. When nothing is needed
|
|
105
|
+
|
|
106
|
+
If the issue is already well-typed, labeled, and complete — or there is otherwise no visible
|
|
107
|
+
change to make — take no action and record that no action was needed. Never close issues.
|
|
@@ -33,7 +33,7 @@ jobs:
|
|
|
33
33
|
private-key: ${{ secrets.PRIMER_APP_PRIVATE_KEY_SHARED }}
|
|
34
34
|
|
|
35
35
|
- name: Set up Node.js
|
|
36
|
-
uses: actions/setup-node@
|
|
36
|
+
uses: actions/setup-node@v6
|
|
37
37
|
with:
|
|
38
38
|
node-version: 24
|
|
39
39
|
|
|
@@ -62,7 +62,7 @@ jobs:
|
|
|
62
62
|
fetch-depth: 0
|
|
63
63
|
|
|
64
64
|
- name: Set up Node.js
|
|
65
|
-
uses: actions/setup-node@
|
|
65
|
+
uses: actions/setup-node@v6
|
|
66
66
|
with:
|
|
67
67
|
node-version: 24
|
|
68
68
|
|
|
@@ -112,7 +112,7 @@ jobs:
|
|
|
112
112
|
fetch-depth: 0
|
|
113
113
|
|
|
114
114
|
- name: Set up Node.js
|
|
115
|
-
uses: actions/setup-node@
|
|
115
|
+
uses: actions/setup-node@v6
|
|
116
116
|
with:
|
|
117
117
|
node-version: 24
|
|
118
118
|
|
package/CHANGELOG.md
CHANGED