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
Copy file name to clipboardExpand all lines: contributing/repository/triaging.md
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -6,17 +6,17 @@ Repository maintainers triage every issue and PR opened in the repository.
6
6
7
7
Issues are opened with one of these labels:
8
8
9
-
-`template: bug` - unverified issue with Next.js itself
10
-
-`template: documentation` - feedback for improvement or an unverified issue with the Next.js documentation
11
-
-`area: examples` - an issue with one of the examples in the [`examples`](https://github.com/vercel/next.js/tree/canary/examples) folder
9
+
-`bug` - issue with Next.js itself
10
+
-`documentation` - feedback for improvement or an issue with the Next.js documentation
11
+
-`example bug` - an issue with one of the examples in the [`examples`](https://github.com/vercel/next.js/tree/canary/examples) folder
12
12
13
13
## Bug reports
14
14
15
15
### Automated triaging
16
16
17
17
In case of a bug report, **if the reproduction is missing or insufficient, the issue is automatically closed**, and a comment is added with a correct course of action. The issue will receive [this comment](https://github.com/vercel/next.js/blob/canary/.github/invalid-link.md). We also add an `invalid link` label to mark the issue. To avoid your issue being closed, please follow the [bug report template](https://github.com/vercel/next.js/blob/canary/.github/ISSUE_TEMPLATE/1.bug_report.yml) carefully.
18
18
19
-
If you filled out the "Which area(s) are affected? (Select all that apply)" section of the bug report template, we will add the corresponding `area:`label(s).
19
+
If you fill out the "Which area(s) are affected? (Select all that apply)" section of the bug report template, we will add the corresponding [label(s)](https://github.com/vercel/next.js/labels).
20
20
21
21
### Manual triaging
22
22
@@ -26,7 +26,7 @@ A maintainer can also manually label an issue with one of the following labels,
26
26
27
27
1.`please add a complete reproduction`
28
28
29
-
The provided reproduction is not enough for the maintainers to investigate. If a sufficient reproduction is not provided for more than 30 days, the issue becomes stale and will be automatically closed. If a reproduction is provided within 30 days, a `needs triage` label is added, indicating that the issue needs another look from a maintainer.
29
+
The provided reproduction is not enough for the maintainers to investigate. If sufficient reproduction is not provided for more than 30 days, the issue becomes stale and will be automatically closed. If a reproduction is provided within 30 days, a `needs triage` label is added, indicating that the issue needs another look from a maintainer.
30
30
31
31
The issue will receive [this comment](https://github.com/vercel/next.js/blob/canary/.github/comments/invalid-reproduction.md)
32
32
@@ -53,7 +53,7 @@ The issue will receive [this comment](https://github.com/vercel/next.js/blob/can
53
53
54
54
## Verified issues
55
55
56
-
If an issue is verified, it will receive the `linear: next`, `linear: dx` or `linear: web` label and will be tracked by the maintainers. Additionally, one or more `area:`label(s) can be added to indicate which part of Next.js is affected.
56
+
If an issue is verified, it will receive the `linear: next`, `linear: dx` or `linear: web` label and will be tracked by the maintainers. Additionally, one or more [label(s)](https://github.com/vercel/next.js/labels) can be added to indicate which part of Next.js is affected.
57
57
58
58
Confirmed issues never become stale or are closed before resolution.
0 commit comments