summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAnirudh Ramanathan <ramanathana@google.com>2017-06-22 10:22:07 -0700
committerGitHub <noreply@github.com>2017-06-22 10:22:07 -0700
commit2038845e1c1aa07c6360f9ed13c2a7b1e8f8a597 (patch)
treeb896dcd0e3a7635e4d643f44b791e0482efacdd6
parent171e7e8a21cb7abf2815f60b044759df27540a9d (diff)
Update on-call-build-cop.md
-rw-r--r--contributors/devel/on-call-build-cop.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/contributors/devel/on-call-build-cop.md b/contributors/devel/on-call-build-cop.md
index ef1d1ccc..bcf7ac70 100644
--- a/contributors/devel/on-call-build-cop.md
+++ b/contributors/devel/on-call-build-cop.md
@@ -9,7 +9,9 @@ The current buildcop can be found [here](https://storage.googleapis.com/kubernet
## Prerequisites for build-copping
-- Ensure you have write access to [http://github.com/kubernetes/kubernetes](http://github.com/kubernetes/kubernetes)
+- Ensure you have admin access to [http://github.com/kubernetes/kubernetes](http://github.com/kubernetes/kubernetes)
+ - Check your membership in the GitHub team: [kubernetes-build-cops](https://github.com/orgs/kubernetes/teams/kubernetes-build-cops/members).
+ If you are not a member contact one of the team maintainers to get yourself added to it.
- Test your admin access by e.g. adding a label to an issue.
- You must communicate any concerns/actions via the **#sig-release** slack channel to ensure that
the release team has context on the current state of the submit queue.