- Owner: @janpio
- Stakeholders: @pantharshit00 @divyenduz
- State:
- Spec: Stable ✅
- Implementation: Fully implemented ✅
Our Prisma Framework repositories use several labels in the Issue Triage process.
To categorize incoming issues:
kind/bug
: A reported bug.kind/regression
: A reported bug in functionality that used to work before.kind/feature
: A request for a new feature.kind/improvement
: An improvement to existing feature and code.kind/docs
: A documentation change is required.kind/discussion
: Discussion is required.kind/question
: Developer asked a question. No code changes required.
To further qualify kind/bug
issues:
bug/0-needs-info
: More information is needed for reproduction.bug/1-repro-available
: A reproduction exists and needs to be confirmed.bug/2-confirmed
: We have confirmed that this is a bug.
The specs
repository has a different set of labels. As this is currently still changing often, it doesn't make too much sense to document here.
The studio
repository has an additional set of labels. As this is currently still changing often, it doesn't make too much sense to document here.
We use an Open Source tool called label-sync
in our prisma-label-sync
repository to define these labels via code and apply the configuration to the GitHub repositories.