Contributing to Next.js

Watch the 40-minute walkthrough video on how to contribute to Next.js. 

• 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.

Signed commits 

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.

Repository 

• Triaging
• Linting
• Release Channels and Publishing
• Pull Request Descriptions

Documentation 

• Adding Documentation

Core 

• Developing
• Building
• Testing
• Adding Error Links
• Adding a new feature
• Developing Using Local App

Turbopack 

• Tracing