- Read about our Commitment to Open Source.
- Before jumping into a PR be sure to search existing PRs or issues for an open or closed item that relates to your submission.
Start with the issue tracker; the good first issue or Documentation labels are a good entry point, but any open issue works.
You do not need permission to work on an issue. For new features, open a discussion and get the proposal accepted first.
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 for more information.
Watch a walkthrough video on how to contribute to Next.js.
This repository requires verified commit signatures on protected branches.
Before contributing, configure Git to sign your commits with a GitHub-verified GPG, SSH, or S/MIME key. Unsigned commits will be rejected by the repository rules and will need to be rewritten as signed commits before they can be merged.
If a pull request includes unsigned commits, re-sign the commits and force-push the branch. Make sure the signing key is added to your GitHub account and that your commits appear as Verified.
A Signed-off-by line in the commit message is not enough to satisfy this requirement.