path: root/wiki
diff options
authorintrigeri <>2019-04-14 06:39:04 +0000
committerintrigeri <>2019-04-14 06:39:26 +0000
commite1a0fe35cd5c60d77aef59a168226fe8a0b25511 (patch)
tree1de5f59e4537e55b1158108114f6d1d19b5bb1d1 /wiki
parent2ef7cd38f74a1d03c28528d0320c65b6e3a2aeb1 (diff)
GitLab: add more ideas inspired from how Qubes OS uses GitHub.
Diffstat (limited to 'wiki')
1 files changed, 6 insertions, 2 deletions
diff --git a/wiki/src/blueprint/GitLab.mdwn b/wiki/src/blueprint/GitLab.mdwn
index 8121d82..8fd031e 100644
--- a/wiki/src/blueprint/GitLab.mdwn
+++ b/wiki/src/blueprint/GitLab.mdwn
@@ -81,7 +81,10 @@ issue, which allows one to find duplicates later on if needed.
- Feature branch: GitLab will automatically link a branch that mentions
an issue.
- Category, Affected Tool, Priority, Status, Type of work → use a set
- of labels for each of them; and maybe simplify a bit
+ of labels, each with a prefix, for each of them; and maybe simplify a bit.
+ For example Qubes uses "P: $priority", "C: $category", etc.
+ One can set multiple labels so we could perhaps merge "Category"
+ and "Affected Tool".
- Log time → Time tracking
- Due date → Due date
- Starter → dedicated label
@@ -143,7 +146,8 @@ of an issues list or issues board filtered by assignee, milestone,
and/or label.
We will need ways to share these URLs and ideally, to name them.
-We can do that on parent tracking tickets, on blueprints, on a team's
+We can do that on the GitLab project's description (home page),
+on parent tracking tickets, on blueprints, on a team's
page on our website, and possibly in GitLab's own
[wiki]( if we decide to
use it (either only for this use case or [[!tails_ticket 9174