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>
1.9 KiB
1.9 KiB
Fix PR
Using the wrong template? — Enhancement: use enhancement.md — Feature: use feature.md
Linked Issue
Required. This PR will be auto-closed if no valid issue link is found.
Fixes #
The linked issue must have the
confirmed-buglabel. If it doesn't, ask a maintainer to confirm the bug before continuing.
What was broken
What this fix does
Root cause
Testing
How I verified the fix
Regression test added?
- Yes — added a test that would have caught this bug
- No — explain why:
Platforms tested
- macOS
- Windows (including backslash path handling)
- Linux
- N/A (not platform-specific)
Runtimes tested
- Claude Code
- Gemini CLI
- OpenCode
- Other: ___
- N/A (not runtime-specific)
Checklist
- Issue linked above with
Fixes #NNN— PR will be auto-closed if missing - Linked issue has the
confirmed-buglabel - Fix is scoped to the reported bug — no unrelated changes included
- Regression test added (or explained why not)
- All existing tests pass (
npm test) .changeset/fragment added if this is a user-facing fix (npm run changeset -- --type Fixed --pr <NNN> --body "...") — orno-changeloglabel applied- No unnecessary dependencies added
Breaking changes
None