Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels 46
-
Document how the algorithm works (internal and/or article publication)
-
Requires an expert to validate the current stage (especially for the design stage)
-
The issue or the merge-request brings a breaking change, that probably needs special attention.
-
Very very dangerous label ! Indicates that a MR should not be merged (Wrong Milestone, ...)
-
Why a MR is not merged yet : author needs to reply to reviewers.
-
Why a MR is not merged yet : Needs a specific feedback for a team members (should be tagged in MR)
-
Why a MR is not merged yet : Needs specific hardware to be tested.
-
Why a MR is not merged yet : needs more work (more than small MR corrections)
-
Qualifies the severity of bugs such as crash, critical security vulnerability, major malfunction, etc...
-
Qualifies the severity of bugs such as minor malfunction, wrong behaviour, but that do not prevent the software from running