@@ -4,9 +4,14 @@ Thanks for your interest in contributing!
44
55## Reporting Issues
66
7- - Search existing issues before opening a new one
8- - Include steps to reproduce, expected vs actual behavior
9- - For bugs, include your OS and relevant versions
7+ Before opening an issue, search existing issues to avoid duplicates.
8+
9+ ** Use the issue templates:**
10+ - ** Bug Report** - Something isn't working as expected
11+ - ** Feature Request** - Suggest a new feature or enhancement
12+ - ** Documentation** - Report missing or unclear docs
13+
14+ Blank issues are disabled - please use one of the templates above.
1015
1116## Development Setup
1217
@@ -77,11 +82,14 @@ Every PR that changes functionality should include a changeset.
7782
7883## Pull Requests
7984
80- 1 . Fork the repo and create your branch from ` main `
81- 2 . Make your changes
82- 3 . Run ` pnpm changeset ` to create a changeset
83- 4 . Test your changes locally
84- 5 . Submit a PR with a clear description
85+ ** Every PR must reference an Issue.** CI will fail if no issue is linked.
86+
87+ 1 . Create an issue first (bug, feature, or docs)
88+ 2 . Fork the repo and create your branch from ` main `
89+ 3 . Make your changes
90+ 4 . Run ` pnpm changeset ` to create a changeset
91+ 5 . Test your changes locally
92+ 6 . Submit a PR with ` Closes #<issue-number> ` in the description
8593
8694## Code Style
8795
0 commit comments