Commit 78654a8c authored by Rémy Coutable's avatar Rémy Coutable

Add missing team and stage labels in the workflow labels doc

Signed-off-by: default avatarRémy Coutable <remy@rymai.me>
parent 6a2e10e3
......@@ -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.
......
......@@ -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:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment