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

Update repo creation instructions

This commit is contained in:
Christoph Blecker 2024-02-26 12:44:52 -08:00
parent df95fc8c9b
commit 50e22e1bec
No known key found for this signature in database
GPG Key ID: B34A59A9D39F838B
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.
* 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-<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)
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).