2 Commits

Author	SHA1	Message	Date
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
Balázs Orbán	3a923d5eda	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](https://github.com/vercel/next.js/blob/b868cf95f29a305bca1afabdb8db76e64a1cce30/.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	2024-01-31 02:50:23 +01:00