Skip to content

Commit 517e67e

Browse files
authored
Merge pull request #12557 from ethereum/needs-triage
Refactor: update "needs triage 📥" GitHub label
2 parents 8e43cfa + 3874b4b commit 517e67e

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

.github/workflows/issue-triage-label.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,5 +17,5 @@ jobs:
1717
issue_number: context.issue.number,
1818
owner: context.repo.owner,
1919
repo: context.repo.repo,
20-
labels: ["needs-triage"]
20+
labels: ["needs triage 📥"]
2121
})

docs/github-issue-triage-process.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,17 +4,17 @@ This documentation outlines the current process for how issues are triaged for t
44

55
## Issue creation process
66

7-
Whenever a new issue is opened, it will automatically be labeled with a `needs-triage` label. The `needs-triage` label means that the core team needs to look at the issue, and nobody should work on it yet to avoid unnecessary work. This label will be removed after the issue has been triaged by a core contributor.
7+
Whenever a new issue is opened, it will automatically be labeled with a `needs triage 📥` label. The `needs triage 📥` label means that the core team needs to look at the issue, and nobody should work on it yet to avoid unnecessary work. This label will be removed after the issue has been triaged by a core contributor.
88

99
## Triage process
1010

11-
The core team will review issues with the `needs-triage` label within 5 days. In order for an issue to be considered triaged, one of the following will need to happen:
11+
The core team will review issues with the `needs triage 📥` label within 5 days. In order for an issue to be considered triaged, one of the following will need to happen:
1212

1313
1. The issue will be closed if it is not needed, a duplicate, or spam.
1414
2. If an issue needs more discussion, the `GH grooming` tag will be added, and the issue will be discussed next GitHub grooming. After this call, action items will be recorded and the issue will be considered triaged.
1515
3. The issue is labeled with the appropriate tags for work needed (ex: `design required`, `dev required`, etc.) and open it up for assignment. More on this below.
1616

17-
After an issue has been triaged, the `needs-triage` label will be removed from the issue.
17+
After an issue has been triaged, the `needs triage 📥` label will be removed from the issue.
1818

1919
## Assignment process
2020

0 commit comments

Comments
 (0)