From a239da55b67d9d0995e893b6bed03ef3c8eb8cbd Mon Sep 17 00:00:00 2001 From: Tomek Mrugalski Date: Mon, 13 Aug 2018 06:07:19 -0400 Subject: [PATCH] Update gitlab howto --- gitlab-howto.md | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/gitlab-howto.md b/gitlab-howto.md index f663302..7d7c0b2 100644 --- a/gitlab-howto.md +++ b/gitlab-howto.md @@ -91,4 +91,19 @@ When migrating stuff between repos, DO NOT copy files over. Use cherry-pick inst **Registration for users is working**. -**We are yet to experience the power of CI**. There will be screams in the process and tears of joy at the end. \ No newline at end of file +**We are yet to experience the power of CI**. There will be screams in the process and tears of joy at the end. + +# Using labels +One major difference,advantage or a flaw (depending on your personal preference) of gitlab is its label system. + +Violet labels are for priority. There are four priority labels: critical, high, medium and low. + +Orange labels are for components. + +Green labels designate type and state of the issue (feature request, QA needed, etc) + +Yellow labels designate specific libraries. + +Red labels are for things that should stand out. Currently there's one label: bug. + +This is just a proposal. Tomek's idea was to use dark colors for important things and light colors for less important aspects. If you don't like it, we can come up with an alternative naming/coloring scheme.