diff options
| author | Anirudh Ramanathan <ramanathana@google.com> | 2017-06-19 11:05:27 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-06-19 11:05:27 -0700 |
| commit | 171e7e8a21cb7abf2815f60b044759df27540a9d (patch) | |
| tree | c32d638810a42d124b97fc1121916f85e0cfd35c | |
| parent | 10ff89c5fad124a7f31edf9abb12e6bf59c82762 (diff) | |
Update on-call-build-cop.md
| -rw-r--r-- | contributors/devel/on-call-build-cop.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/contributors/devel/on-call-build-cop.md b/contributors/devel/on-call-build-cop.md index af680374..ef1d1ccc 100644 --- a/contributors/devel/on-call-build-cop.md +++ b/contributors/devel/on-call-build-cop.md @@ -36,9 +36,9 @@ that those builds are green and allowing merges to occur. causes for the failure. Debug if possible, else triage and assign to a particular SIG, and @-mention the maintainers. For example, see: [https://github.com/kubernetes/kubernetes/issues/47135](https://github.com/kubernetes/kubernetes/issues/47135) -4. Communicate the actions to # **sig-release** via slack and ensure that the issue is being worked on. +4. Communicate the actions to **#sig-release** via slack and ensure that the issue is being worked on. 1. If the issue is not worked on for several hours, please escalate to the release team. 5. When the SIG member sends a fix, manually merge if necessary, after verifying that pre-submits pass, or use the 'retest-not-required' label with the appropriate 'queue/*' label to ensure merge of the flake fix. -6. Issue an update to the # **sig-release** channel on the merge rate and the PR that was used to fix the queue. +6. Issue an update to the **#sig-release** channel on the merge rate and the PR that was used to fix the queue. |