74a19b7467
docs: unify the header deps by removing # ( #72391 )
...
## Summary
Remove redundant `#` from [error
pages](https://github.com/vercel/next.js/tree/canary/errors ).
## Description
Follow up #52038 and #72263 .
Updated
[template.txt](https://github.com/vercel/next.js/blob/canary/errors/template.txt )
and clarified the header deps.
Then rewrite as per the template.
### Improving Documentation
- [x] Run `pnpm prettier-fix` to fix formatting issues before opening
the PR.
- [x] Read the Docs Contribution Guide to ensure your contribution
follows the docs guidelines:
https://nextjs.org/docs/community/contribution-guide
Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com >
2024-11-07 08:58:43 +00:00
fddd022e1b
docs: fix broken link of new comments path ( #71674 )
...
# Summary
Add missing comments path to which #61416 changed.
### Improving Documentation
- [x] Run `pnpm prettier-fix` to fix formatting issues before opening
the PR.
- [x] Read the Docs Contribution Guide to ensure your contribution
follows the docs guidelines:
https://nextjs.org/docs/community/contribution-guide
Co-authored-by: JJ Kasper <jj@jjsweb.site >
2024-10-29 11:54:28 -07:00
60c07208dd
chore(docs/errors): Improve documentation grammar ( #60452 )
...
This PR fixes a couple of typos found in the docs/errors section
---------
Co-authored-by: Steven <steven@ceriously.com >
2024-01-10 16:48:29 +00:00
d5c35a1bbb
chore: replace issue triaing actions with nissuer ( #55525 )
...
### What?
Moving maintenance to a separate repository.
### Why?
I want to make these actions reusable in other projects as they seem to work well in the Next.js repository.
### How?
The code is moved to https://github.com/balazsorban44/nissuer
I tested it on my fork, and all the following functionality is preserved: https://github.com/balazsorban44/next.js/issues/56
- [x] Close/lock/comment without a valid reproduction link
- [x] Minimize "+1"
- [x] Add labels based on user selection
- [x] Add comment based on the maintainer's label (eg.: "please add a complete reproduction")
2023-09-19 11:11:00 +00:00
0f07cf5798
chore: verify missing/invalid/private reproduction links ( #54724 )
...
### What?
This PR adds a new action that verifies if the reproduction link is correct _after_ the issue has been created. If it is not, we close the issue and comment on it with the correct steps to take. Check out the [rendered comment here](https://github.com/balazsorban44/next.js/blob/chore/gh-invalid-link-checker/.github/actions/issue-validator/repro-link/invalid-link.md ).
Additionally, this PR also does some refactoring to simplify our GitHub actions related to issues.
Tests:
Issue that was supposed to be closed:
- https://github.com/balazsorban44/next.js/issues/48
- Issue comment: https://github.com/balazsorban44/next.js/issues/48#issuecomment-1698836121
- Issue opened action: https://github.com/balazsorban44/next.js/actions/runs/6023209630
- Issue labeled action: https://github.com/balazsorban44/next.js/actions/runs/6023209629
Issue that was not supposed to be closed (closed manually afterward):
- https://github.com/balazsorban44/next.js/issues/49
- Issue opened action: https://github.com/balazsorban44/next.js/actions/runs/6023214256
- Issue labeled action: https://github.com/balazsorban44/next.js/actions/runs/6023214258
### Why?
Unfortunately, GitHub is currently missing the [functionality to require a valid reproduction link](https://github.com/orgs/community/discussions/10227 ) in issue templates. Even if that was supported, this PR adds functionality that could not be covered with a regex validation. Namely, we check if the reproduction is a private repo or not, and potentially could also check the structure to see if it's an actual Next.js project.
### How?
If the link is not in the expected section, not a GitHub, CodeSandbox, or Replay.io link, or does not return an OK response (eg.: private repo/sandbox), the issue is closed/commented.
Related:
- https://github.com/orgs/community/discussions/4629
- https://github.com/orgs/community/discussions/10227
Co-authored-by: Steven <229881+styfle@users.noreply.github.com >
2023-08-30 17:40:57 +00:00
44d1a1cb15
docs: Migrate error messages to MDX and App Router. ( #52038 )
...
This PR is part of a larger effort to migrate error messages to MDX and
use App Router: https://github.com/vercel/front/pull/23459
2023-07-05 06:11:16 -07:00
Jam Balaya