summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSarrah Vesselov <svesselov@gitlab.com>2018-06-14 14:45:19 +0000
committerSarrah Vesselov <svesselov@gitlab.com>2018-06-14 14:45:19 +0000
commitbc60412ded5b47bd0fa9c91d6fd97b7308f6a5fb (patch)
tree8c3e4aa1f10f4bc632db0a5bbb104c6306525db5
parentea891fb3ad930a5df1f0021ef1513098de86545b (diff)
downloadgitlab-ce-bc60412ded5b47bd0fa9c91d6fd97b7308f6a5fb.tar.gz
clarify ux label processux-label-update
-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.