skills/vercel__next.js
1
0
Fork 0
mirror of https://github.com/vercel/next.js.git synced 2026-09-20 02:25:18 +08:00
Code Issues Packages Projects Releases Wiki Activity

Link to issues in the contribution guide and discourage trivial PRs (#97188)

Browse Source 
I just reviewed 10+ prs from @marcoshernanz landing trivial edit fixes
(on behalf of contributors) and outside of Documentation we really
shouldn't encourage this

Also, im guessing a link to the issue tracker is more useful than a 40
minute YouTube video
This commit is contained in:
Luke Sandberg
2026-08-12 14:55:50 -07:00
committed by GitHub
parent 13491b0d08
commit 10fe9bea76
1 changed files with 14 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
contributing.md
+14 -2
View File
@@ -1,10 +1,22 @@
# Contributing to Next.js
[Watch the 40-minute walkthrough video on how to contribute to Next.js.](https://www.youtube.com/watch?v=cuoNzXFLitc)
- Read about our [Commitment to Open Source](https://vercel.com/oss).
- Before jumping into a PR be sure to search [existing PRs](https://github.com/vercel/next.js/pulls) or [issues](https://github.com/vercel/next.js/issues) for an open or closed item that relates to your submission.
## What to contribute
Start with the issue tracker; the [`good first issue`](https://github.com/vercel/next.js/labels/good%20first%20issue) or [Documentation](https://github.com/vercel/next.js/labels/Documentation) labels are a good entry point, but any [open issue](https://github.com/vercel/next.js/issues) works.
You do not need permission to work on an issue. For new **features**, open a [discussion](https://github.com/vercel/next.js/discussions/new?category=ideas) and get the proposal accepted first.
## Trivial changes
Every pull request has to be reviewed by a maintainer. Automation helps, but it does not eliminate that: someone still has to read the change and decide it is correct. Reviewer attention is the scarcest resource the project has. Trivial PRs such as typo fixes, formatting, or code style changes are likely to be closed. For the Next.js documentation (under `docs/`) we are more open to such changes; see the [Docs Contribution Guide](https://nextjs.org/docs/community/contribution-guide) for more information.
## Walkthrough video
[Watch a walkthrough video on how to contribute to Next.js.](https://www.youtube.com/watch?v=cuoNzXFLitc)
## Signed commits
This repository requires verified commit signatures on protected branches.