mirror of
https://github.com/bevyengine/bevy
synced 2024-11-22 04:33:37 +00:00
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>
This commit is contained in:
parent
50bba0f595
commit
78b67906c9
1 changed files with 9 additions and 0 deletions
|
@ -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.
|
||||
|
||||
|
|
Loading…
Reference in a new issue