From 50e22e1bec2e22f641287f6c5530998810f78fc8 Mon Sep 17 00:00:00 2001 From: Christoph Blecker Date: Mon, 26 Feb 2024 12:44:52 -0800 Subject: [PATCH] Update repo creation instructions --- github-management/org-owners-guide.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/github-management/org-owners-guide.md b/github-management/org-owners-guide.md index 8d3ef70ab..6aabb7598 100644 --- a/github-management/org-owners-guide.md +++ b/github-management/org-owners-guide.md @@ -176,16 +176,17 @@ a new repository are described below. [SIG Repository], add a labels entry for the SIG that the repo belongs to. * Update the `SECURITY_CONTACTS` file as per the request. Note that aliases cannot be used in this case so expand the team, if specified. - * Create a new commit with the message *Update OWNERS, OWNERS_ALIASES and + * Update the `README.md` file with the name and description of the repo. + * Create a new commit with the message *Update README, OWNERS, OWNERS_ALIASES and SECURITY_CONTACTS*. * Push the new commit directly to the master branch. * If the repo is a [SIG Repository], add a new topic of the form - `k8s-sig-` using the *Manage Topics* option. + `k8s-sig-` using *Topics* under the + Repository section of the org-level settings page. * Create a PR against [kubernetes/org] to add teams as per the [team guidance](#team-guidance) for alloting repo admin and write access. * Once the above PR is merged and the postsubmit has run, the new GitHub teams - will be created. In the *Collaborators and Teams* section in Settings, - assign the new teams appropriate access to the repo. + will be created and should have access automatically assiged by peribolos. * Ask the author of the repo creation request to add the repo as a part of a subproject in [`sigs.yaml`](/sigs.yaml).