github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-08-01 07:47:56 +00:00
Code Issues Projects Releases Wiki Activity

clarify weekend responsibilities

Browse Source
This commit is contained in:
Matt Liggett 2016-09-09 15:56:54 -07:00
parent f5077ff806
commit 7ad362bb3c
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/devel/on-call-build-cop.md
View File

@ -139,7 +139,7 @@ or [flaky test builds](https://goto.google.com/k8s-test/view/Flaky/) are not
your responsibility to monitor. The `Test owner:` in the job description will be your responsibility to monitor. The `Test owner:` in the job description will be
automatically emailed if the job is failing. automatically emailed if the job is failing.
* If you are a weekday oncall, ensure that PRs confirming to the following * If you are oncall, ensure that PRs confirming to the following
pre-requisites are being merged at a reasonable rate: pre-requisites are being merged at a reasonable rate:
* [Have been LGTMd](https://github.com/kubernetes/kubernetes/labels/lgtm) * [Have been LGTMd](https://github.com/kubernetes/kubernetes/labels/lgtm)
@ -147,10 +147,9 @@ pre-requisites are being merged at a reasonable rate:
* Author has signed CLA if applicable. * Author has signed CLA if applicable.
* If you are a weekend oncall, [never merge PRs manually](collab.md), instead * Although the shift schedule shows you as being scheduled Monday to Monday,
add the label "lgtm" to the PRs once they have been LGTMd and passed Travis; working on the weekend is neither expected nor encouraged. Enjoy your time
this will cause merge-bot to merge them automatically (or make them easy to find off.
by the next oncall, who will merge them).
* When the build is broken, roll back the PRs responsible ASAP * When the build is broken, roll back the PRs responsible ASAP