From 5392f616b4f0dc072bece831dc7cd9b4ae518ce8 Mon Sep 17 00:00:00 2001 From: David Baker Date: Wed, 14 Jul 2021 22:15:18 +0100 Subject: [PATCH] Use existing issues labels / scheme Co-authored-by: J. Ryan Stinnett --- CONTRIBUTING.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index ba0d3af23..8f684e8dc 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -80,10 +80,10 @@ Notes: Remove legacy `Camelopard` class. `Giraffe` should be used instead. ``` Other metadata can be added using labels. - * `pr-breaking`: A breaking change - adding this label will mean the change causes a *major* version bump. - * `pr-feature`: A new feature - adding this label will mean the change causes a *minor* version bump. - * `pr-bugfix`: A bugfix (in either code or docs). - * `pr-internal`: No user-facing changes, eg. code comments, CI fixes, refactors or tests. Won't have a changelog entry unless you specify one. + * `X-Breaking`: A breaking change - adding this label will mean the change causes a *major* version bump. + * `T-Enhancement`: A new feature - adding this label will mean the change causes a *minor* version bump. + * `T-Defect`: A bug fix (in either code or docs). + * `T-Task`: No user-facing changes, eg. code comments, CI fixes, refactors or tests. Won't have a changelog entry unless you specify one. If you don't have permission to add labels, your PR reviewer(s) can work with you to add them: ask in the PR description or comments.