-
-
Notifications
You must be signed in to change notification settings - Fork 31
Dev: Issues
Pablo Mayrgundter edited this page Feb 8, 2024
·
3 revisions
A good issue is:
- Focused: one logical/holistic change. Less is more
- Clear: Write a good description that describes the context, goal and next steps
- Demonstrated: Screens or examples for comparison help a lot
- Creator is responsible for status, unless there's an assignee. Creator closes issue, just like PR.
- Leave assignee open unless you self-assign or have checked with the assignee that they're ready for new work.
- Always set labels and Projects.
- Prefer issues to ask about or update status. Discord and email comms are lower priority.
- Creator closes issue, just like PR. Include a good description for why the issue was closed, including PR # or duplicate issue #