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

List the best practices on configuring staging repo 

As discussed in https://github.com/kubernetes/test-infra/pull/34209 we want those best practices applied for all staging repositories
This commit is contained in:
Sergey Kanzhelev 2025-01-29 09:25:13 -08:00 committed by GitHub
parent 7712817748
commit ecf7ebfe61
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
contributors/devel/sig-architecture/staging.md
View File

@ -24,8 +24,17 @@ a published repo, the code you get is exactly the same as if you check out the
It is recommend to use the semver `v0.x.y` tags for a seamless experience
with go modules.
## Configuring Staging Repositories
If further repos under staging are needed, adding them to the bot is easy.
Contact one of the [owners of the bot](https://git.k8s.io/publishing-bot/OWNERS).
Currently, the bot is hosted on a
[public CNCF cluster](https://github.com/kubernetes/publishing-bot/blob/master/production.md).
As staging repository is not designed for direct contributions it is recommended to:
1. Make sure README.md in the root folder explicitly stating that contributions (issues and PRs)
must be done to the Kubernetes repository, not to the staging copy.
3. Request to disable issues on the repository (like this [example](https://github.com/kubernetes/org/issues/5370)).
4. Block PRs using prow bot (like this [example](https://github.com/kubernetes/test-infra/pull/34209)).