mirror of
https://github.com/vercel/next.js.git
synced 2026-09-20 02:25:18 +08:00
Benjamin Woodruff
0cfc85ceae
## Summary Documents the policy around AI-assisted contributions, for both humans and agents: - `.github/pull_request_template.md`: notes that AI use is encouraged for researching, creating, and reviewing changes, but contributors must deeply understand their contributions, and PR descriptions from external contributors must be written by a human. - `.github/ISSUE_TEMPLATE/1.bug_report.yml`: adds the equivalent note for bug reports — issue descriptions from external contributors must be written by a human, though AI may help create reproductions. - `AGENTS.md`: replaces the old "PR Descriptions" section with two new sections. "GitHub Pull Requests" distinguishes branch PRs (agents may write descriptions) from fork PRs targeting `vercel/next.js` (agents may not). "GitHub Issues, Comments, and Discussions" restricts agent-written issues, discussions, and comments to members of the `vercel`/`vercel-labs` GitHub orgs, tells agents how to check membership via the GitHub API, lists what agents can still help non-members with (drafting details, reviewing, reproductions, translation, searching for duplicates), and carves out exceptions (commenting on the user's own PR, Vercel-operated bots, GitHub/Graphite review bots, and forks of the repo). - Renames the LLM watermark marker from `NEXT_JS_LLM_PR` to `NEXT_JS_LLM` everywhere it appears (`AGENTS.md`, `contributing/repository/pull-request-descriptions.md`, and the `create-pr`/`backport-pr` skills), since it now also applies to issues, discussions, and comments. Nothing in the repo consumes the old marker name. - `.agents/skills/create-pr/SKILL.md`: adds a "Fork PRs vs Branch PRs" section referencing the `AGENTS.md` policy. Assorted typo fixes along the way. ## Verification - `gh api /user/memberships/orgs` and `gh api orgs/vercel/members/<login>` (confirmed the documented membership checks work and return the documented statuses) - Not run: no test/build commands (docs-only change; prettier applied via the pre-commit hook) <!-- NEXT_JS_LLM -->
52 lines
2.3 KiB
Markdown
52 lines
2.3 KiB
Markdown
<!-- Thanks for opening a PR! Your contribution is much appreciated.
|
|
To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below.
|
|
Choose the right checklist for the change(s) that you're making:
|
|
|
|
## For Contributors
|
|
|
|
We encourage you to use AI to assist you in researching, creating, and reviewing changes. However, you must review and deeply understand the contributions you are making. For this reason, **pull request descriptions from external contributors must be written by a human**.
|
|
|
|
### Improving Documentation
|
|
|
|
- Run `pnpm prettier-fix` to fix formatting issues before opening the PR.
|
|
- Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide
|
|
|
|
### Fixing a bug
|
|
|
|
- Related issues linked using `fixes #number`
|
|
- Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
|
|
- Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md
|
|
|
|
### Adding a feature
|
|
|
|
- Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas)
|
|
- Related issues/discussions are linked using `fixes #number`
|
|
- e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
|
|
- Documentation added
|
|
- Telemetry added. In case of a feature if it's used or not.
|
|
- Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md
|
|
|
|
### Signed commits
|
|
|
|
- This repository requires verified commit signatures on protected branches.
|
|
- If this pull request is blocked for unsigned commits, re-sign the commits and force-push the branch.
|
|
- A `Signed-off-by` line in the commit message is not enough.
|
|
|
|
## For Maintainers
|
|
|
|
- Minimal description (aim for explaining to someone not on the team to understand the PR)
|
|
- When linking to a Slack thread, you might want to share details of the conclusion
|
|
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
|
|
- Add review comments if necessary to explain to the reviewer the logic behind a change
|
|
|
|
### What?
|
|
|
|
### Why?
|
|
|
|
### How?
|
|
|
|
Closes NEXT-
|
|
Fixes #
|
|
|
|
-->
|