diff options
| author | Rémy Coutable <remy@rymai.me> | 2019-04-10 17:44:57 +0200 |
|---|---|---|
| committer | Rémy Coutable <remy@rymai.me> | 2019-04-10 17:53:15 +0200 |
| commit | 78654a8c6aea0fc6cfdf82e191dfc209e0adb4e2 (patch) | |
| tree | c9343f939b99eb7ed0542bb909563119a9501973 | |
| parent | 6a2e10e38ba87678b6b44fa73786eb1f4a668a4e (diff) | |
| download | gitlab-ce-78654a8c6aea0fc6cfdf82e191dfc209e0adb4e2.tar.gz | |
Add missing team and stage labels in the workflow labels doc
Signed-off-by: Rémy Coutable <remy@rymai.me>
| -rw-r--r-- | doc/development/contributing/issue_workflow.md | 4 | ||||
| -rw-r--r-- | doc/development/testing_guide/flaky_tests.md | 4 |
2 files changed, 6 insertions, 2 deletions
diff --git a/doc/development/contributing/issue_workflow.md b/doc/development/contributing/issue_workflow.md index 4c53643ed9c..827b3d7681a 100644 --- a/doc/development/contributing/issue_workflow.md +++ b/doc/development/contributing/issue_workflow.md @@ -62,10 +62,12 @@ The current team labels are: - ~Configure - ~Create +- ~Defend - ~Distribution - ~Documentation - ~Geo - ~Gitaly +- ~Growth - ~Manage - ~Monitor - ~Plan @@ -99,6 +101,8 @@ The current stage labels are: - ~"devops:configure" - ~"devops:monitor" - ~"devops:secure" +- ~"devops:defend" +- ~"devops:enablement" These labels should be mutually exclusive. If an issue belongs to multiple stages, the most relevant should be used. diff --git a/doc/development/testing_guide/flaky_tests.md b/doc/development/testing_guide/flaky_tests.md index 3d568c37fba..931cbc51cae 100644 --- a/doc/development/testing_guide/flaky_tests.md +++ b/doc/development/testing_guide/flaky_tests.md @@ -8,7 +8,7 @@ eventually. ## Quarantined tests When a test frequently fails in `master`, -[a ~"broken master" issue](https://about.gitlab.com/handbook/engineering/workflow/#broken-master) +[a ~"master:broken" issue](https://about.gitlab.com/handbook/engineering/workflow/#broken-master) should be created. If the test cannot be fixed in a timely fashion, there is an impact on the productivity of all the developers, so it should be placed in quarantine by @@ -21,7 +21,7 @@ bin/rspec --tag quarantine ``` **Before putting a test in quarantine, you should make sure that a -~"broken master" issue exists for it so it won't stay in quarantine forever.** +~"master:broken" issue exists for it so it won't stay in quarantine forever.** Once a test is in quarantine, there are 3 choices: |