3657c4ea9e
The three PR templates still asked contributors to tick `CHANGELOG.md updated`, contradicting the post-#2978 rule (documented in CONTRIBUTING.md and enforced by scripts/changeset/lint.cjs) that `CHANGELOG.md` must not be edited directly. Each checkbox now references `npm run changeset` with the appropriate `--type` (Fixed/Changed/Added) and notes the `no-changelog` opt-out label where applicable, so `gh pr create` users land in the correct workflow by copy-paste. Closes #3006 Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
3.4 KiB
3.4 KiB
Feature PR
Using the wrong template? — Bug fix: use fix.md — Enhancement to existing behavior: use enhancement.md
Linked Issue
Required. This PR will be auto-closed if no valid issue link is found. The linked issue must have the
approved-featurelabel. If it does not, this PR will be closed without review — no exceptions.
Closes #
⛔ No
approved-featurelabel on the issue = immediate close. Do not open this PR if a maintainer has not yet approved the feature spec. Do not open this PR if you wrote code before the issue was approved.
Feature summary
What changed
New files
| File | Purpose |
|---|---|
Modified files
| File | What changed |
|---|---|
Implementation notes
Spec compliance
Testing
Test coverage
Platforms tested
- macOS
- Windows (including backslash path handling)
- Linux
Runtimes tested
- Claude Code
- Gemini CLI
- OpenCode
- Codex
- Copilot
- Other: ___
- N/A — specify which runtimes are supported and why others are excluded
Scope confirmation
- The implementation matches the scope approved in the linked issue exactly
- No additional features, commands, or behaviors were added beyond what was approved
- If scope changed during implementation, I updated the issue spec and received re-approval
Checklist
- Issue linked above with
Closes #NNN— PR will be auto-closed if missing - Linked issue has the
approved-featurelabel — PR will be closed if missing - All acceptance criteria from the issue are met (listed above)
- Implementation scope matches the approved spec exactly
- All existing tests pass (
npm test) - New tests cover the happy path, error cases, and edge cases
.changeset/fragment added with a user-facing description of the feature (npm run changeset -- --type Added --pr <NNN> --body "...")- Documentation updated — commands, workflows, references, README if applicable
- No unnecessary external dependencies added
- Works on Windows (backslash paths handled)
Breaking changes
None