chore: add resolved
label (#61416)
### What?
- Add a comment to issues labeled with `resolved`
Note to maintainers: it won't autoclose the issue. (This would need to
be added to [`nissuer`](https://github.com/balazsorban44/nissuer) as a
new feature)
Rendered comment
[here](b868cf95f2/.github/good-first-issue.md
)
- I also reorganized the label comments to its own folder since we have
a few now.
### Why?
After verifying if an open issue has been fixed, a common task is to
comment on it and tell people to upgrade or open a new issue if it
persists. (Ideally, PRs would reference every issue they fix, but
sometimes we need to do this chore manually)
### How?
Using `nissuer`'s
[comment-label](https://github.com/balazsorban44/nissuer#label-management).
Closes NEXT-2306
This commit is contained in:
parent
44b589e8ec
commit
3a923d5eda
8 changed files with 23 additions and 13 deletions
5
.github/comments/resolved.md
vendored
Normal file
5
.github/comments/resolved.md
vendored
Normal file
|
@ -0,0 +1,5 @@
|
||||||
|
This issue has been resolved on a newer version of the package. Please update to `next@latest` or `next@canary` to test it out!
|
||||||
|
|
||||||
|
If you think this issue was closed by mistake, or the issue still persists on the newest version, please open a new issue with the latest version of the package.
|
||||||
|
|
||||||
|
Thank you!
|
|
@ -1,4 +1,4 @@
|
||||||
name: Validate issue
|
name: Triage issues
|
||||||
|
|
||||||
on:
|
on:
|
||||||
issues:
|
issues:
|
||||||
|
@ -14,22 +14,22 @@ permissions:
|
||||||
|
|
||||||
jobs:
|
jobs:
|
||||||
triage:
|
triage:
|
||||||
name: Auto triage issue
|
name: Nissuer
|
||||||
runs-on: ubuntu-latest
|
runs-on: ubuntu-latest
|
||||||
steps:
|
steps:
|
||||||
- name: Nissuer
|
- uses: balazsorban44/nissuer@1.8.2
|
||||||
uses: balazsorban44/nissuer@1.8.2
|
|
||||||
with:
|
with:
|
||||||
label-area-prefix: 'area:'
|
label-area-prefix: 'area:'
|
||||||
label-area-section: 'Which area\(s\) are affected\? \(Select all that apply\)(.*)### Additional context'
|
label-area-section: 'Which area\(s\) are affected\? \(Select all that apply\)(.*)### Additional context'
|
||||||
label-comments: |
|
label-comments: |
|
||||||
{
|
{
|
||||||
"please add a complete reproduction": ".github/invalid-reproduction.md",
|
"good first issue": ".github/comments/good-first-issue.md",
|
||||||
"please simplify reproduction": ".github/simplify-reproduction.md",
|
"please add a complete reproduction": ".github/comments/invalid-reproduction.md",
|
||||||
"please verify canary": ".github/verify-canary.md",
|
"please simplify reproduction": ".github/comments/simplify-reproduction.md",
|
||||||
"good first issue": ".github/good-first-issue.md"
|
"please verify canary": ".github/comments/verify-canary.md",
|
||||||
|
"resolved": ".github/comments/resolved.md"
|
||||||
}
|
}
|
||||||
reproduction-comment: '.github/invalid-link.md'
|
reproduction-comment: '.github/comments/invalid-link.md'
|
||||||
reproduction-hosts: 'github.com,codesandbox.io'
|
reproduction-hosts: 'github.com,codesandbox.io'
|
||||||
reproduction-blocklist: 'github.com/vercel/next.js.*,github.com/\\w*/?$,github.com$'
|
reproduction-blocklist: 'github.com/vercel/next.js.*,github.com/\\w*/?$,github.com$'
|
||||||
reproduction-link-section: '### Link to the code that reproduces this issue(.*)### To Reproduce'
|
reproduction-link-section: '### Link to the code that reproduces this issue(.*)### To Reproduce'
|
|
@ -28,23 +28,28 @@ A maintainer can also manually label an issue with one of the following labels,
|
||||||
|
|
||||||
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.
|
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.
|
||||||
|
|
||||||
The issue will receive [this comment](https://github.com/vercel/next.js/blob/canary/.github/invalid-reproduction.md)
|
The issue will receive [this comment](https://github.com/vercel/next.js/blob/canary/.github/comments/invalid-reproduction.md)
|
||||||
|
|
||||||
2. `please verify canary`
|
2. `please verify canary`
|
||||||
|
|
||||||
The issue is not verified against the `next@canary` release. The canary version of Next.js ships daily and includes all features and fixes that have not been released to the stable version yet. Think of canary as a public beta. Some issues may already be fixed in the canary version, so please verify that your issue reproduces before opening a new issue. Issues not verified against `next@canary` will be closed after 30 days.
|
The issue is not verified against the `next@canary` release. The canary version of Next.js ships daily and includes all features and fixes that have not been released to the stable version yet. Think of canary as a public beta. Some issues may already be fixed in the canary version, so please verify that your issue reproduces before opening a new issue. Issues not verified against `next@canary` will be closed after 30 days.
|
||||||
|
|
||||||
The issue will receive [this comment](https://github.com/vercel/next.js/blob/canary/.github/verify-canary.md)
|
The issue will receive [this comment](https://github.com/vercel/next.js/blob/canary/.github/comments/verify-canary.md)
|
||||||
|
|
||||||
3. `please simplify reproduction`
|
3. `please simplify reproduction`
|
||||||
|
|
||||||
The provided reproduction is too complex or requires too many steps to reproduce. If a simplified 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.
|
The provided reproduction is too complex or requires too many steps to reproduce. If a simplified 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.
|
||||||
The issue will receive [this comment](https://github.com/vercel/next.js/blob/canary/.github/simplify-reproduction.md)
|
The issue will receive [this comment](https://github.com/vercel/next.js/blob/canary/.github/comments/simplify-reproduction.md)
|
||||||
|
|
||||||
4. `good first issue`
|
4. `good first issue`
|
||||||
|
|
||||||
The issue is considered beginner-friendly enough to be a good starting point for someone new to the project who wants to contribute.
|
The issue is considered beginner-friendly enough to be a good starting point for someone new to the project who wants to contribute.
|
||||||
The issue will receive [this comment](https://github.com/vercel/next.js/blob/canary/.github/good-first-issue.md)
|
The issue will receive [this comment](https://github.com/vercel/next.js/blob/canary/.github/comments/good-first-issue.md)
|
||||||
|
|
||||||
|
5. `resolved`
|
||||||
|
|
||||||
|
We assume that a newer version of Next.js fixed the issue. If the issue is still relevant, please open a new issue and reference the old one.
|
||||||
|
The issue will receive [this comment](https://github.com/vercel/next.js/blob/canary/.github/comments/resolved.md)
|
||||||
|
|
||||||
## Verified issues
|
## Verified issues
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue