Mirrors/bevy
2
0
Fork 0
mirror of https://github.com/bevyengine/bevy synced 2024-09-20 06:22:01 +00:00
Code Issues Projects Releases Packages Wiki Activity

Added meaning of issue label prefixes (#7705)

Browse source 
# 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>
This commit is contained in:
Adam 2023-02-18 07:22:21 +00:00
parent 50bba0f595
commit 78b67906c9
1 changed files with 9 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
CONTRIBUTING.md
View file

@ -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.