mirror of https://github.com/vercel/next.js.git synced 2026-09-20 02:25:18 +08:00

Files

T

Marcos Hernanz 7a5d2f9f32 Allow issue participants to request reopening (#96947 )

## Summary

- Let issue authors and people who commented before closure reopen an
issue within 14 days using `Reopen: <reason>`.
- Limit the automation to unlocked issues closed by triage-or-higher
human maintainers, with ordered timeline checks, bot filtering,
idempotency, and state revalidation.
- Align resolved-issue and contributor guidance with the new reopening
window.

## Verification

- `Prettier 3.6.2 --check .github/workflows/issue_reopen.yml
.github/comments/resolved.md contributing/repository/triaging.md`
- Mocked workflow harness covering 19 closure, eligibility, boundary,
bot, idempotency, and race scenarios
- `autoreview --mode local --stream-engine-output` (Codex and Claude
clean)
- Live GitHub API spot-check for ordered same-second `commented` and
`closed` timeline events
- Not run: live issue close/reopen smoke test (issue-triggered workflows
run only from the default branch)

2026-08-12 15:34:54 -07:00

4.4 KiB

Raw Permalink Blame History

Triaging

Repository maintainers triage every issue and PR opened in the repository.

Note: Feature requests should be opened as discussions, filling out this template.

Issues are opened with one of these labels:

bug - issue with Next.js itself
documentation - feedback for improvement or an issue with the Next.js documentation
examples - an issue with one of the examples in the examples folder

Bug reports

Automated triaging

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. We also add an invalid link label to mark the issue. To avoid your issue being closed, please follow the bug report template carefully.

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).

Manual triaging

If the issue is specific to the project and not to Next.js itself, it will be converted to a 🎓️ Help discussion

A maintainer can also manually label an issue with one of the following labels, which will also add a comment with a correct course of action:

please add a complete reproduction

The provided reproduction is not enough for the maintainers to investigate. If a sufficient reproduction is not provided, the issue will be automatically closed after 2 days of inactivity.

The issue will receive this comment

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 automatically closed after 14 days of inactivity.

The issue will receive this comment

please simplify reproduction

The provided reproduction is too complex or requires too many steps to reproduce. If a simplified reproduction is not provided, the issue will be automatically closed after 14 days of inactivity. The issue will receive this comment

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 will receive this comment

resolved

We assume that a newer version of Next.js fixed the issue. If a maintainer closes the issue and it is still relevant, the issue author or someone who commented before it was closed can request that it be reopened within 14 days by following the automated comment. The issue will receive this comment

Verified issues

If an issue is verified, it will receive the linear: next, linear: turbopack or linear: docs label and will be tracked by the maintainers. Additionally, one or more label(s) can be added to indicate which part of Next.js is affected.

Confirmed issues never become stale or are closed before resolution.

Closed issues

When a maintainer closes an unlocked issue, an automated comment explains how the issue author or someone who commented before it was closed can request that it be reopened within 14 days. The request must include Reopen: and a reason.

All closed PRs and Issues will be locked after 2 weeks of inactivity (eg.: comment, referencing from elsewhere). After the reopening window expires, please open a new issue with up-to-date details and reference the old one. Automated closures provide their own next steps.

4.4 KiB Raw Permalink Blame History Unescape Escape