summaryrefslogtreecommitdiff
path: root/contributors
diff options
context:
space:
mode:
authorMaria Ntalla <mntalla@pivotal.io>2019-02-08 13:17:17 +0000
committerMaria Ntalla <mntalla@pivotal.io>2019-02-08 13:17:17 +0000
commit2720cc0ae1b1bd4a16dbf89c90a4d4393fa299a9 (patch)
tree29c5aaafa4ed85af81355b412568e2e92e9d737b /contributors
parent2b06c05299a13af618c1c69fa0a6a0ba5233acb6 (diff)
Capitalize words, format commands as code
Diffstat (limited to 'contributors')
-rw-r--r--contributors/devel/testing.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/contributors/devel/testing.md b/contributors/devel/testing.md
index 7053e536..e9f0acb8 100644
--- a/contributors/devel/testing.md
+++ b/contributors/devel/testing.md
@@ -238,8 +238,8 @@ Click on `Details` and look at the [`gubernator`](gubernator.k8s.io/) output for
- If no, open a new issue and notify the appropriate SIG (see: Escalating failures to a SIG)
#### Escalating failures to a SIG
-- Figure out corresponding sig from test name/description
-- Mention the sig's github handle on the issue, optionally cc the SIG's chair(s) (locate them under kubernetes/community/sig-<name>)
+- Figure out corresponding SIG from test name/description
+- Mention the SIG's GitHub handle on the issue, optionally `cc` the SIG's chair(s) (locate them under kubernetes/community/sig-<name\>)
- Optionally (or if you haven't heard back on the issue after 24h) reach out to the SIG on slack
### Testgrid
@@ -261,4 +261,4 @@ It is useful as a way to:
- dashboards
- collection of jobs
- each dashboard is represented as a button
- - some dashboards collect jobs/tests in the domain of a specific SIG (named after and owned by those sigs), and dashboards to monitor project wide health (owned by sig-release)
+ - some dashboards collect jobs/tests in the domain of a specific SIG (named after and owned by those SIGs), and dashboards to monitor project wide health (owned by SIG-release)