-
Notifications
You must be signed in to change notification settings - Fork 75
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
Document recommended repo setup #2
Comments
In the kubernetes-incubator org, ACL teams are named admins-repo and maintainers-repo. I prefer repo-admins (admin), repo-maintainers (write), and repo-collaborators (read). The teams are sorted alphabetically on the github UI, so putting the repo first groups them together. It's also handier for auto-completion. |
@sarahnovotny I think I wrote something somewhere at sometime. Do you remember where we put that? |
Issues go stale after 30d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
/remove-lifecycle rotten |
@spiffxp is working on related issues |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/close |
Forked from kubernetes/kops#644
I think it would be useful to describe the recommended setup for repos in the template.
For example, admin and maintainers (write) teams.
And how to turn on the bot. And copy labels.
And OWNERS.
Etc
cc @grodrigues3
The text was updated successfully, but these errors were encountered: