From b0809cf5d71e502746d9c1a72d0a9e25dacf96ef Mon Sep 17 00:00:00 2001 From: Nikhita Raghunath Date: Thu, 4 Oct 2018 16:55:31 +0530 Subject: [PATCH] Make staging repo creation instructions clearer --- staging/README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/staging/README.md b/staging/README.md index e56a44c8280..be2a8d9c3f1 100644 --- a/staging/README.md +++ b/staging/README.md @@ -63,7 +63,7 @@ for creating the staging repository. 4. Update [`hack/import-restrictions.yaml`](https://github.com/kubernetes/kubernetes/blob/master/hack/import-restrictions.yaml) to add the list of other staging repos that this new repo can import. -5. Add all mandatory template files mentioned in +5. Add all mandatory template files to the staging repo as mentioned in https://github.com/kubernetes/kubernetes-template-project. 6. Make sure that the `.github/PULL_REQUEST_TEMPLATE.md` and @@ -81,6 +81,8 @@ for an example. 2. Setup branch protection and enable access to the `stage-bots` team by adding the repo in [`prow/config.yaml`](https://github.com/kubernetes/test-infra/blob/master/prow/config.yaml). +See [#kubernetes/test-infra#9292](https://github.com/kubernetes/test-infra/pull/9292) +for an example. 3. Once the repository has been created in the Kubernetes org, update the publishing-bot to publish the staging repository by updating: