mirror of
https://github.com/different-ai/openwork
synced 2026-04-25 17:15:34 +02:00
36 lines
1.2 KiB
Markdown
36 lines
1.2 KiB
Markdown
# Issue Triage Rubric
|
|
|
|
This document defines how maintainers triage issues consistently.
|
|
|
|
## Core type labels
|
|
|
|
- `bug`: behavior does not match expected behavior.
|
|
- `enhancement`: improvement to existing behavior.
|
|
- `question`: support or usage request.
|
|
|
|
Apply exactly one core type label whenever possible.
|
|
|
|
## Contribution-oriented labels
|
|
|
|
- `good first issue`: small, well-scoped, low-risk, and has clear acceptance criteria.
|
|
- `help wanted` or `help needed`: maintainers welcome external contributions.
|
|
- `needs-info`: issue cannot be actioned until reporter provides missing details.
|
|
|
|
## Suggested triage flow
|
|
|
|
1. Confirm issue template fields are complete.
|
|
2. Add a core type label (`bug`, `enhancement`, or `question`).
|
|
3. Add scope/difficulty labels if helpful.
|
|
4. Add `needs-info` when reproduction details are missing.
|
|
5. Add `good first issue` or `help wanted/help needed` only when issue is ready to build.
|
|
|
|
## Closing guidance
|
|
|
|
Close as:
|
|
|
|
- `duplicate`: issue already tracked elsewhere.
|
|
- `invalid`: report is not actionable or not a product issue.
|
|
- `wontfix`: acknowledged but not planned.
|
|
|
|
When closing, include a short reason and a link to related issue/docs when available.
|