vercel__next.js

skills/vercel__next.js

Fork 0

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

Commit Graph

Author SHA1 Message Date

Author	SHA1	Message	Date
Tim Neutkens	dd0cae63e0	Align issue triage guidance with automated behavior (#94189 ) ### What? - Align the public triage guide with the issue workflows current response windows and confirmed-team labels. - Update reproduction and canary response comments to describe automatic closure separately from the later lock workflow. ### Why? The documented triage contract had drifted from the active automation: the guide described 30-day response windows and unsupported triage labeling, while automated comments implied that timed closure immediately locks issues. This sets inaccurate expectations for reporters and maintainers. ### How? Update the four Markdown surfaces that explain manual triage and automated follow-up behavior to match the existing stale and lock workflows. ### Verification - `pnpm prettier --with-node-modules --ignore-path .prettierignore --check contributing/repository/triaging.md .github/comments/invalid-reproduction.md .github/comments/simplify-reproduction.md .github/comments/verify-canary.md` - `git diff --cached --check` - Not run: `pnpm --filter=next build` (`documentation and GitHub comment text only; no framework source changes`) <!-- NEXT_JS_LLM_PR -->	2026-05-28 13:24:18 +02:00
Sam Ko	41378d01e2	chore(github): update comments stale period (#74291 ) ## Why? Since we updated the stale waiting period in https://github.com/vercel/next.js/pull/73709, we need to update these comments as well.	2024-12-26 15:07:58 -08: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

Tim Neutkens

dd0cae63e0

Align issue triage guidance with automated behavior (#94189 )

### What?

- Align the public triage guide with the issue workflows current
response windows and confirmed-team labels.
- Update reproduction and canary response comments to describe automatic
closure separately from the later lock workflow.

### Why?

The documented triage contract had drifted from the active automation:
the guide described 30-day response windows and unsupported triage
labeling, while automated comments implied that timed closure
immediately locks issues. This sets inaccurate expectations for
reporters and maintainers.

### How?

Update the four Markdown surfaces that explain manual triage and
automated follow-up behavior to match the existing stale and lock
workflows.

### Verification

- `pnpm prettier --with-node-modules --ignore-path .prettierignore
--check contributing/repository/triaging.md
.github/comments/invalid-reproduction.md
.github/comments/simplify-reproduction.md
.github/comments/verify-canary.md`
- `git diff --cached --check`
- Not run: `pnpm --filter=next build` (`documentation and GitHub comment
text only; no framework source changes`)

<!-- NEXT_JS_LLM_PR -->

2026-05-28 13:24:18 +02:00

Sam Ko

41378d01e2

chore(github): update comments stale period (#74291 )

## Why?

Since we updated the stale waiting period in https://github.com/vercel/next.js/pull/73709, we need to update these comments as well.

2024-12-26 15:07:58 -08: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

3 Commits