-
Notifications
You must be signed in to change notification settings - Fork 687
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
config: Init kubernetes-nightly org #3131
Conversation
Signed-off-by: Stephen Augustus <foo@auggie.dev>
Signed-off-by: Stephen Augustus <foo@auggie.dev>
Signed-off-by: Stephen Augustus <foo@auggie.dev>
Signed-off-by: Stephen Augustus <foo@auggie.dev>
Signed-off-by: Stephen Augustus <foo@auggie.dev>
8bf11ac
to
d3f2cbd
Compare
/hold until k8s-github-robot is an org owner for https://github.com/kubernetes-nightly
/assign @cblecker @mrbobbytables |
Docs update: kubernetes/community#6271 |
/lgtm |
727391d
to
8203dba
Compare
/hold cancel FYI @kubernetes/owners @kubernetes/publishing-bot-maintainers @kubernetes/release-engineering |
From @kubernetes/release-engineering |
/hold I'll take a look at this tomorrow. Want to watch that peribolos run closely when we bootstrap a new org. |
has_repository_projects: true | ||
members_can_create_repositories: false | ||
billing_email: github@kubernetes.io | ||
admins: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One question @justaugustus -- if there are teams that have access to the repos, do we need to have all the release managers as org admins here too? Wondering if there is a technical reason :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One question @justaugustus -- if there are teams that have access to the repos, do we need to have all the release managers as org admins here too? Wondering if there is a technical reason :)
Currently, only members of the @kubernetes/owners + @kubernetes/publishing-bot-admins (pub-bot approvers + @kubernetes/sig-release-admins) are listed as org admins.
Our default repo creation permission is:
members_can_create_repositories: false
Given the kubernetes-nightly
org exists to test the creation of repos, some subset of SIG Release needs access to do so.
As we learn more (and get the process documented), we can probably start to:
- automate more (bot account + GCB job (or something))
- revisit org admins
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds great! Thanks @justaugustus !
- Add k8s-publishing-bot (member) Signed-off-by: Stephen Augustus <foo@auggie.dev>
8203dba
to
63affa6
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cblecker, justaugustus The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Part of kubernetes/sig-release#1772.
Signed-off-by: Stephen Augustus foo@auggie.dev
Slack convo: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1638832884428700