kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #7733 from cblecker/rcu 

Update repo creation instructions
This commit is contained in:
Kubernetes Prow Robot 2024-02-26 13:12:48 -08:00 committed by GitHub
parent c96ddbca7a 50e22e1bec
commit 8f35516cc1
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
github-management/org-owners-guide.md
View File

@ -176,16 +176,17 @@ a new repository are described below.
[SIG Repository], add a labels entry for the SIG that the repo belongs to. [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 * Update the `SECURITY_CONTACTS` file as per the request. Note that aliases
cannot be used in this case so expand the team, if specified. 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*. SECURITY_CONTACTS*.
* Push the new commit directly to the master branch. * Push the new commit directly to the master branch.
* If the repo is a [SIG Repository], add a new topic of the form * If the repo is a [SIG Repository], add a new topic of the form
`k8s-sig-<sig-name-repo-belongs-to>` using the *Manage Topics* option. `k8s-sig-<sig-name-repo-belongs-to>` 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) * Create a PR against [kubernetes/org] to add teams as per the [team guidance](#team-guidance)
for alloting repo admin and write access. for alloting repo admin and write access.
* Once the above PR is merged and the postsubmit has run, the new GitHub teams * 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, will be created and should have access automatically assiged by peribolos.
assign the new teams appropriate access to the repo.
* Ask the author of the repo creation request to add the repo * Ask the author of the repo creation request to add the repo
as a part of a subproject in [`sigs.yaml`](/sigs.yaml). as a part of a subproject in [`sigs.yaml`](/sigs.yaml).