diff options
| author | Rémy Coutable <remy@rymai.me> | 2017-05-05 14:48:53 +0000 |
|---|---|---|
| committer | Rémy Coutable <remy@rymai.me> | 2017-05-05 14:48:53 +0000 |
| commit | 672278ba0fd9b74ba649bd54cfba967c3b13eb46 (patch) | |
| tree | e20f26d142e5cc36d92b430cca81f05148bb13c9 | |
| parent | f62afa01b1b9b73d9a30bf5125ac9a39e6be0e01 (diff) | |
| parent | 4a681bb19f672e2266f0863db73706977727523a (diff) | |
| download | gitlab-ce-672278ba0fd9b74ba649bd54cfba967c3b13eb46.tar.gz | |
Merge branch 'remove-frontend-team-label' into 'master'
Remove FE team label
See merge request !11119
| -rw-r--r-- | CONTRIBUTING.md | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 600dad563a6..8b6c87ae518 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -21,7 +21,7 @@ _This notice should stay as the first item in the CONTRIBUTING.MD file._ - [Workflow labels](#workflow-labels) - [Type labels (~"feature proposal", ~bug, ~customer, etc.)](#type-labels-feature-proposal-bug-customer-etc) - [Subject labels (~wiki, ~"container registry", ~ldap, ~api, etc.)](#subject-labels-wiki-container-registry-ldap-api-etc) - - [Team labels (~CI, ~Discussion, ~Edge, ~Frontend, ~Platform, etc.)](#team-labels-ci-discussion-edge-frontend-platform-etc) + - [Team labels (~CI, ~Discussion, ~Edge, ~Platform, etc.)](#team-labels-ci-discussion-edge-platform-etc) - [Priority labels (~Deliverable and ~Stretch)](#priority-labels-deliverable-and-stretch) - [Label for community contributors (~"Accepting Merge Requests")](#label-for-community-contributors-accepting-merge-requests) - [Implement design & UI elements](#implement-design--ui-elements) @@ -155,18 +155,21 @@ Examples of subject labels are ~wiki, ~"container registry", ~ldap, ~api, Subject labels are always all-lowercase. -### Team labels (~CI, ~Discussion, ~Edge, ~Frontend, ~Platform, etc.) +### Team labels (~CI, ~Discussion, ~Edge, ~Platform, etc.) Team labels specify what team is responsible for this issue. Assigning a team label makes sure issues get the attention of the appropriate people. The current team labels are ~Build, ~CI, ~Discussion, ~Documentation, ~Edge, -~Frontend, ~Gitaly, ~Platform, ~Prometheus, ~Release, and ~"UX". +~Gitaly, ~Platform, ~Prometheus, ~Release, and ~"UX". The descriptions on the [labels page][labels-page] explain what falls under the responsibility of each team. +Within those team labels, we also have the ~backend and ~frontend labels to +indicate if an issue needs backend work, frontend work, or both. + Team labels are always capitalized so that they show up as the first label for any issue. |