summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorClement Ho <clemmakesapps@gmail.com>2018-06-14 16:26:31 +0000
committerClement Ho <clemmakesapps@gmail.com>2018-06-14 16:26:31 +0000
commitb3969ed23cbda79eea138fea3a23921703795543 (patch)
tree12e31f1bea6d50836476a75ad07e0d8948c364d0
parentc00cc23578bd73e0c65e1dcb7e3528366eb5f2e9 (diff)
parentbc60412ded5b47bd0fa9c91d6fd97b7308f6a5fb (diff)
downloadgitlab-ce-b3969ed23cbda79eea138fea3a23921703795543.tar.gz
Merge branch 'ux-label-update' into 'master'
clarify ux label process See merge request gitlab-org/gitlab-ce!19854
-rw-r--r--CONTRIBUTING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index fb78973a727..ec904ada5bc 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -303,7 +303,7 @@ The UX team uses labels to manage their workflow.
The ~"UX" label on an issue is a signal to the UX team that it will need UX attention.
To better understand the priority by which UX tackles issues, see the [UX section](https://about.gitlab.com/handbook/engineering/ux) of the handbook.
-Once an issue has been worked on and is ready for development, a UXer applies the ~"UX ready" label to that issue.
+Once an issue has been worked on and is ready for development, a UXer removes the ~"UX" label and applies the ~"UX ready" label to that issue.
The UX team has a special type label called ~"design artifact". This label indicates that the final output
for an issue is a UX solution/design. The solution will be developed by frontend and/or backend in a subsequent milestone.