From 78b67906c927c658deef06d98304befbf08001a2 Mon Sep 17 00:00:00 2001 From: Adam Date: Sat, 18 Feb 2023 07:22:21 +0000 Subject: [PATCH] Added meaning of issue label prefixes (#7705) # Objective Fixes #7704 ## Solution Added a small section that describes the meaning of each letter prefix for issue labels. Co-authored-by: Adam <59033400+adam-shih@users.noreply.github.com> --- CONTRIBUTING.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index c360d723a8..ec8e8cf772 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -81,6 +81,15 @@ Our merge strategy relies on the classification of PRs on two axes: * How controversial are the design decisions * How complex is the implementation +Each [label](https://github.com/bevyengine/bevy/labels) has a prefix denoting its category: + +* A: Area (e.g. A-Animation, A-ECS, A-Rendering) +* C: Category (e.g. C-Breaking-Change, C-Code-Quality, C-Docs) +* D: Difficulty (e.g. D-Complex, D-Good-First-Issue) +* O: Operating System (e.g. O-Linux, O-Web, O-Windows) +* P: Priority (e.g. P-Critical, P-High) +* S: Status (e.g. S-Blocked, S-Controversial, S-Needs-Design) + PRs with non-trivial design decisions are given the [`S-Controversial`] label. This indicates that the PR needs more thorough design review or an [RFC](https://github.com/bevyengine/rfcs), if complex enough.